Monthly Archives: August 2013
Most of you, using Windows Phone 7 or Windows Phone 8 with at least 2 accounts on your device may face the following issue…
All new calendar entries default to Windows Live. Wait a minute…I have an exchange account…and I want to see that calendar in my company’s Outlook!!! Windows live? I assume this is done by purpose since Microsoft wants to boost its new company coordination regarding services over the cloud.
Anyway there are 2 ways to overcome this:
The first workaround is to hit settings inside your Calendar and disable other calendars except the one you want to keep (simply slide the bar to the left…yea-yea this iPhone alike button 😛 ) . This will result that only your enabled calendar will be displayed, therefore whatever you add, it will only update your enabled calendar. After saving at least one calendar, AND SYNC, you may hit settings again and re-enable other calendars in case you want me. (For example I want my FB calendar to be displayed for events I participate). It seems that Windows Phone calendar default to the one LAST used!!!! I say it seems, since I think I have noticed otherwise as well….
The second way that appears to be handier is by pushing the (+) add button. Apparently I don’t use it since I tend to press on the calendar screen repeatedly in order to add a new appointment. Well eventually if you click (+) then the menu has an option for updating a specific calendar. Following up the previous solution, once you save on one calendar then Windows phone calendar defaults to the one last updated.
The truth is always out there Mr….trial and error will make you find it. Be creative…
This may appear when linking SQL tables in MS Access through ODBC.
Although Microsoft recommends connecting to tables through code, ODBC has always been a fast way to do it.
First of all don’t be upset, no truncation is actually taking place on your data backend, Access is just unable to display the numeric value’s, due to a change you did on the SQL table. Don’t be that sure that you did no change…since this may come from a query/view involving more than one tables. It needs at least one problematic field and the message appears.
I got a good workaround of this, without removing tables and relinking in Access which actually did not work for me. The idea is too find the problematic numeric field. My case was a change of a decimal (18,2) field simply to decimal (18,5). I found the view that was the control source of the form (linked in Access), copied aside the views code and removed the decimal fields that had the problem. Went back on Access and refreshed this problematic view only. Went back again on the Sql view and pasted the code as it was originally copied, NO CHANGE!!! Go back in Access and refresh this particular link and your problem is gone.
Let me go home now, or I will be a divorced poor IT guy…