July 16, 2009 22:33 by
joze
Yesterday I received an invitation to Microsoft® Office 2010 Technical Preview Program. 
Really great piece of software so far - it brings us some interesting improvements like ribbon in Outlook and Visio, new Office menu,...
At first I was really happy to join this program but after only one day I already encountered few problems. And I solved them all :)
The biggest and most irritating was when Outlook didn't display Reading Pane - it was showing folders and I was able to select them but there was no list of folder content and no Reading Pane. The only working solution was to fully uninstall and then install Office 2010 (tried Reinstall with no success). I have no idea why this has happened - it could be because of some extension for Outlook 2007 or something completely different (I Installed Office 2010 on my system where there was already Office 2007 and I didn't upgrade or uninstall it - same goes for all extensions for Office apps).
And here we come to the second problem - coexistence of two Microsoft Office Word versions. If you had at any point in past on your system two Word versions you have surly encountered this problem. When you use one of them and then you run the other one you always have to wait for that annoying window to close (something like "Please wait while Word is configuring") - but no more! The solution I'm going to tell you about is pretty simple. Actually I'm going to show you two different solutions with the same effect :) And none of them involves any kind of virtual system.
The first one is really easy: all you have to do is to run the other Word (the one you don't use often) with /a switch. You can create new shortcut with target value of something like:
"c:\Program Files (x86)\Microsoft Office\Office12\WINWORD.EXE" /a
or you can add /a switch to your existing shortcut in Start menu.
This switch is intended to start Word and prevent add-ins and global templates (including the Normal template) from being loaded automatically. The /a switch also locks the setting files; that is, the setting files cannot be read or modified if you use this switch. You can find more useful switches in KB 210565.
The second solution is for those who like to edit registry. You have to create new DWORD (32-bit) value named NoRereg with value data equal to 1 at:
- HKEY_CURRENT_USER\Software\Microsoft\Office\12.0\Word\Options (Word 2007),
- HKEY_CURRENT_USER\Software\Microsoft\Office\11.0\Word\Options (Word 2003),
- HKEY_CURRENT_USER\Software\Microsoft\Office\10.0\Word\Options (Word 2002) or
- HKEY_CURRENT_USER\Software\Microsoft\Office\9.0\Word\Options (Word 2000).
Second solution is better because it doesn't limit your daily work in any way.
99d79152-c5c9-441b-858a-ea492b61140c|2|5.0
July 15, 2009 21:20 by
RobiI opened a new Word document in MS Word 2007 and started typing. I noticed that all defaults for paragraphs, fonts and generally formatting are gone.
So in order to reset all formatting to defaults you have to delete or rename a certain file.
In Vista, that file is in: C:\Users\[yourname]\AppData\Roaming\Microsoft\Templates
in that folder delete or rename file normal.dotm
If you want to reset all settings to factory defaults you have to delete a registry key for MS Word. For each version of MS Word the registry key is slightly different and is as follows:
Word 2007
HKEY_CURRENT_USER\Software\Microsoft\Office\12.0\Word
Word 2003
HKEY_CURRENT_USER\Software\Microsoft\Office\11.0\Word
Word 2002
HKEY_CURRENT_USER\Software\Microsoft\Office\10.0\Word
Word 2000
HKEY_CURRENT_USER\Software\Microsoft\Office\9.0\Word
you can read more at:
http://support.microsoft.com/kb/822005
Voila!
9982e4de-6c1d-4c66-9b90-bac82140ed16|1|5.0
July 14, 2009 19:29 by
RobiHi,
For all of you SharePoint fans and geeks a must see videos @
http://sharepoint.microsoft.com/2010/Sneak_Peek/Pages/default.aspx
Enjoy!
323075c8-56f4-410e-a318-00e94584c875|1|5.0
If you've ever tried testing SQL stored procedures and functions, you've undoubtedly run into situations where you needed to clear tables of data to load fixtures into related tables. In MySQL, this would be accomplished by using TRUNCATE on the child tables, going up the hierarchy; in MS SQL, you cannot use TRUNCATE on tables that are referenced by foreign keys.
To remedy the situation, consider the scenario where you have two tables – Child and Parent. The Child table contains a foreign key referencing the primary key in Parent. In this case, you can use the following code snippet to truncate both tables:
TRUNCATE TABLE Child;
DELETE FROM Parent;
DBCC CHECKIDENT(Parent, RESEED, 0);
This will clear the table data and reset the primary key increment variable to 0. Any new data in the tables will now start enumeration on autoincrement numeric primary keys with 1.
799fa68d-412a-47cd-85d6-3bdb0f407ee2|1|5.0
The easyest was is to create a new role and then just add users to that role:
CREATE ROLE db_executor
GRANT EXECUTE TO db_executor TO db_executor
6afbb9f8-db8d-4b8d-a6ec-745208b4d48b|2|5.0