Jeff Johnson wrote:
> I have multi-site applications where the database name and table structures
> are the same and different sites are stored in different folders.
>
>  
>
>             Application\Site1\files.dbc
>
>             Application\Site2\files.dbc
>
>                         Etc.
>
>  
>
> I have been doing this for a long time, only now I have a new app that is
> consolidating data from all sites.  VFP only recognizes one dbc name
> regardless of how many are open with that name.
>
>  
>
> I can open .\site1\files.dbc and .\site2\files.dbc.  I can "SET DATABASE TO
> .\site2\files.dbc" and it will not change from site1.  This is related to a
> thread I started a couple of weeks ago about backing up a dbc.
>
>  
>
> Does anyone know of a work around?  I guess the only solution at this point
> is to modify everything to open up tables by full path rather than
> dbc!table.
>   

I had a similar issue back in the late 90s iirc (and that was VFP5/6!).  
My workaround was to create a temporary database locally called TempDBC 
and then move from SourceDBC to TempDBC and then from TempDBC to 
TargetDBC.  Not sure if that helps you or not?  Certainly it lengthens 
the operation since you're using a 3rd entity, but that's what worked 
for me way back when.

hth,
--Mike

-- 
Michael J. Babcock, MCP
MB Software Solutions, LLC
http://mbsoftwaresolutions.com
http://fabmate.com
"Work smarter, not harder, with MBSS custom software solutions!"



_______________________________________________
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.

Reply via email to