Anita Smith
anitatiedemann at gmail.com
Thu Apr 2 17:23:51 CDT 2009
David, I'm wondering what would happen if you modified the shortcut that opens your application to include the runtime option. PathToAccess PathToAccessFile /runtime I always use that to get rid of the message that Access will be opened in read only mode. Anita Smith On Fri, Apr 3, 2009 at 8:28 AM, David Emerson <newsgrps at dalyn.co.nz> wrote: > Hi Team, > > I have received this information: > "Citrix creates a new application instance per session. If an opened > file creates a lock file then I don't believe there is any way around > this short of creating multiple instances." > > It seems strange that the file should be locked if separate instances > are created. I wonder if it is because the AccessXP application is > being run through an Access 2003 runtime? The Client 1 below is > using an Access XP runtime, the other two are using Access 2003. > > Regards > > David > > At 26/03/2009, you wrote: > >This is more for clarification than anything else. > > > >I have a couple of clients: > > > >Client 1: Access XP ade using SQL2000 BE over terminal services. > >Client 2: Access XP ade using SQL2005 BE over Citrix > >Client 3: Access XP ade using SQL2005 BE over remote desktop. > > > > From Microsoft help > >http://support.microsoft.com/default.aspx?scid=kb;en-us;322762 they say: > > > >When users in a multiuser environment try to open a Microsoft Access > >project (.adp) file or a Microsoft Access project extension (.ade) > >file, they may receive an error message similar to the following: > >The database DatabaseName will be opened read-only because one of the > >following occurred: The file is locked for editing by another user, > >or the file (or the folder in which it is located) is marked as > >read-only, or you specified that you wanted to open this file read-only. > >This behavior is by design. An Access project is strictly a client > >and has no multiuser capability. > > > > > >In the situation of Client 1 there is no problem with multiple users > >opening the same file, but in the other two cases the clients get the > >error message. Is this because Terminal server actually opens > >separate instances of the FE whereas the other two cases are trying > >to open the same physical file? > > > > > >Regards > > > >David Emerson > >Dalyn Software Ltd > >Wellington, New Zealand > > -- > AccessD mailing list > AccessD at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/accessd > Website: http://www.databaseadvisors.com >