I think the point was not to install Legacy in My Documents, but to have the *data* files saved there.
Gary Templeman ----- Original Message ----- From: Mary Boyd To: [email protected] Sent: Monday, June 22, 2009 12:35 PM Subject: Re: [LegacyUG] V7 runtime permission errors in XP Steve, The permission errors seem to have disappeared since Legacy V7 was installed in the MyDocuments folder of the limited user. Thanks again for your suggestion. It seems to have been 'spot on'. Cheers, Mary ------------------------------------------------------------------------------ From: Mary Boyd <[email protected]> To: [email protected] Sent: Monday, June 22, 2009 11:40:10 AM Subject: Re: [LegacyUG] V7 runtime permission errors in XP Steve, Thank you. I think your idea is a good one.. I will play around with installing in locations other than the "default". Cheers, Mary ------------------------------------------------------------------------------ From: Steve Voght <[email protected]> To: [email protected] Sent: Monday, June 22, 2009 10:30:17 AM Subject: Re: [LegacyUG] V7 runtime permission errors in XP Mary, The problem you describe here is almost certainly due to the default location Legacy uses to save its database files (within its own program folder), which is not the way Microsoft instructs third-party software vendors to design their software. Instead, user files (such as your family file) are supposed to be saved within the user folder (e.g. "My Documents" for a Windows machine). This becomes compounded by Legacy defaulting to installing in an unusual location (C:\Legacy) rather than c:\Program Files\Legacy, which puts it into a privileged space that Administrators have full access to, but regular users do not. I'm quite surprised that you can even create a database file within that space as a limited-access user! This is something that the programmers should probably address in a future release, because it creates security concerns and also complicates making backups because the user files aren't saved in a standard location that most backup programs look in, such as your My Documents folder. Try saving your database to a different folder that your limited-access user has full read/write privileges for, such as your My Documents folder, and see if you still have the problems you report here. -Steve On Mon, Jun 22, 2009 at 9:53 AM, Mary Boyd <[email protected]> wrote: Thanks to everyone for your advice and suggestions. Rest assured that I have investigated, read, and tried the “Error by numbers” support information on the Legacy website. I am using XP Home Edition, Service Pack 3. I have it set for automatic updates and it seems to be current. I am still having some problems with Legacy V7 related to using an XP “limited” user account vs. an administrator account. I would appreciate your help figuring out how to fix this. Specifically, when I try to do a File Maintance > Check/Repair with the limited account. I get the following errors during the Check/Repair operation: “The Microsoft Jet database engine cannot open the file C:\Legacy\Legacy1..dbm. It is already opened exclusively by another user, or you need permission to view its data. Would you like to try again?” “Error closing files. Error 91: Object variable or With block variable not set.” “Error rebuilding indexes. Error 91: Object variable or With block variable not set.” Then, a couple more repeats of the above 91 errors, ending with … “Error in Check/Repair of Family File.” “Error 3356: You attempted to open a database that is already opened exclusively by user ‘admin’ on machine ‘XXX’. Try again when the database is available.” Then, finally, “Runtime error 91”, followed by Legacy aborting. I can run this SAME operation from an administrator account and get NO errors whatsoever. Am I then correct in assuming that the problem is NOT my family file(s), but something with how the software is interacting with my system environment? Unfortunately, after running the Check/Repair from the administrator account, I’m not permitted to use the family file in the limited account. Rather it forces me to create a new file and the fun starts all over again. I have tried exporting to a new family file but it did not fix the errors. I have uninstalled Version 7 completely (deleted all files and folders) and reinstalled it, but the results are still the same. BTW, I’m using the most current build of V7, just downloaded it yesterday. Thanks in advance for any further suggestions you might have for me. Cheers, Mary Legacy User Group guidelines: http://www.LegacyFamilyTree.com/Etiquette.asp Archived messages: http://www.mail-archive.com/[email protected]/ Online technical support: http://www.LegacyFamilyTree.com/Help.asp To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp Legacy User Group guidelines: http://www.LegacyFamilyTree.com/Etiquette.asp Archived messages: http://www.mail-archive.com/[email protected]/ Online technical support: http://www.LegacyFamilyTree.com/Help.asp To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp Legacy User Group guidelines: http://www.LegacyFamilyTree.com/Etiquette.asp Archived messages: http://www.mail-archive.com/[email protected]/ Online technical support: http://www.LegacyFamilyTree.com/Help.asp To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp
