> -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > On Behalf Of Ricardo Aráoz > Sent: Friday, May 18, 2007 5:50 PM > To: [EMAIL PROTECTED] > Subject: Re: Multiple Databases Same Name > > Jeff Johnson wrote: > >> -----Original Message----- > >> From: [EMAIL PROTECTED] [mailto:profoxtech- > [EMAIL PROTECTED] > >> On Behalf Of Ricardo Aráoz > >> Sent: Friday, May 18, 2007 4:26 PM > >> To: [EMAIL PROTECTED] > >> Subject: Re: Multiple Databases Same Name > >> > >> Jeff Johnson wrote: > >>>> -----Original Message----- > >>>> From: [EMAIL PROTECTED] [mailto:profoxtech- > >> [EMAIL PROTECTED] > >>>> On Behalf Of Andrew Stirling > >>>> Sent: Friday, May 18, 2007 12:31 PM > >>>> To: [EMAIL PROTECTED] > >>>> Subject: Re: Multiple Databases Same Name > >>>> > >>>> Jeff > >>>> > >>>> I use the same format for my payroll. > >>>> I only let them go into 1 client at a time. > >>>> I shut the database when they choose to go into a new client. > >>>> The new client then gets to have the PATH changed to that folder. > Thus > >>>> you can open & shut the Database to your hearts content as they > always > >>>> find it again via the PATH. > >>>> > >>>> Andrew Stirling > >>>> 01250 874580 > >>>> http://www.calcpay.co.uk > >>>> HMRC Accredited UK payroll program > >>> Thanks Andrew & Michael. I had figured as much, but I "backup" two > very > >>> large files which is more like synchronization than a backup. I have > to > >>> figure out a way to collect the changes, close one and open the other, > >> then > >>> apply the changes. > >>> > >> I don't know if I'm getting it right. But why bother with the > databases? > >> Couldn't you let the databases to be opened automatically and just deal > >> with the tables? > >> e.g.: use Application\Site1\file1.dbf alias Table11 > >> use Application\Site2\file1.dbf alias Table21 etc. > >> and then you deal with the tables. > >> > > > > Ricardo, My whole application is written around the dbc. I use views > and > > all of my use statements look like this: USE dbc!table. For this > > procedure, though, it sounds like that is the way to go. > > Don't know if it works but would "use Application\Site1\dbc!file1 alias > Table11" work? >
That will work for my project but I need to make sure I close the dbc. I discovered that, while tables can have aliases, the dbc can not. If you have a dbc opened you can put any path in front of it you want. It will always use the last one opened. You can't do SET DATABASE TO c:\path\dbc.dbc. You also can't open it again without closing it. It will only set it to one name. So in a sense the dbc name is the alias. The lesson I have learned from this is that you can only have one database open with the same name at the same time or you will get unpredictable results. I have been having a problem with this type of application on terminal services when users switch sites. This helped me identify the problem I have been having. Jeff Jeff Johnson [EMAIL PROTECTED] 623-582-0323 Fax 623-869-0675 --- StripMime Report -- processed MIME parts --- multipart/signed text/plain (text body -- kept) application/x-pkcs7-signature --- _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[EMAIL PROTECTED] ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
