Jeff Johnson wrote: > > 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. > (Coming in late...) Can you have a unique view name in each DBC (it doesn't need to be used, just have a unique name), use ADATABASES() to cycle through the open databases, testing for the existence of said view?
Bill _______________________________________________ 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.
