Justina,

We actually figured this one out - We don't understand why we have to do what where doing it works. The solution was to close the database before we begin the views. Every went smooth after that (like a hot knife through butter).

...and yes, you are the big dog - at least that's what the girls in Las Vegas say!


>Vicky,

>Would ADBOBJECTS(laConNames, "CONNECTION") be helpful??? See ya at Tommy's >after the game...

>-Justin


>Here's the situation:
>
>I created a DSN to connect to a VFP Database through ODBC. I left the database field empty because I'm gonna use it in a connection string to make a connection in a VFP Database. (ya, ya... sounds strange to make a connection to connect to a VFP Database - due to circumstances beyond our control it has to be this way - it's a whole different topic in itself.)
>
>The problem that I'm having is that when I run GenDBC to create the database everything runs perfect. The tables are created. Keys are generated. Even the connection is created using the connection string... However, when it comes time to make the Remote Views I get an error 1526 (connectivity error). When we step through the code and verify the connection the remote view are created successfully and everyone is happy.
>
>The solution is that we have to verify the connection but we can't have any interface while doing this. Verification has to be done programmatically.
>
>Does anyone know how to do this??? Any help would be appreciated.
I AM the Big Dog...