Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Upsizing - VFP 5 to SQL Server 7
Message
De
11/05/1999 17:30:19
Cheryl Qualset
Qualset Computer Consulting
Davis, Californie, États-Unis
 
 
À
06/05/1999 14:48:48
Mark Ganchrow
Dataware Technology Group, Ltd.
Rochester, New York, États-Unis
Information générale
Forum:
Visual FoxPro
Catégorie:
Client/serveur
Divers
Thread ID:
00215821
Message ID:
00217485
Vues:
13
>Can this be done? I've done the following:
>Installed SQL Server Desktop edition on my Window 98 PC.
>Created the database for my app in SQL Server.
>Created a System DSN in ODBC Administrator for SQL Server and my new database.
>
>When I run the upsizing wizard, it find the DSN as an ODBC data source and it asks me to log in. After I log in, it gives me the following message:
>To upsize to SQL Server 6.x, please install a SQL Server ODBC Driver version 2.05 or later
>
>There are 2 things wrong here:
>1. I'm upsizing to SQL Server 7, not 6.x
>2. The ODBC administrator shows the SQL Server ODBC driver as version 3.7.
>
>So...
>Can this (upsizing VFP 5 to SQL Server 7) be done?
>
>And once it is (even if I have to go to VFP 6, which is do-able), what's the best way for getting the SQL database and its accompanying info to the client site? Does the DSN need to be set up on each PC that will be running this app?
>
>Thanks
>mganchrow@networks-inc.net

Are you wondering how to create a SQL Server database from a SQL Server database, or how to create a SQL Server database from a VFP database?

I have not done anything with SQL 7. With this version, I hear, you can copy a SQL database like any other file. (I have used the upsizing wizard from vfp5 to sql6.5 with no trouble.)

Can you connect to the SQL database using your DSN? For example,
create a table in your sql database,
create a connection in the VFP database using your DSN to connect, and then
create a remote view of your table using the connection.
Can you USE the remote view and see an empty table, or does it give you the same ODBC error?

If you can connect, you can append (append from, insert, delete, update...) vfp data to a remote view and TABLEUPDATE() to commit it. You can also send SQL statements to execute on the server to create tables there. This is what the wizard does for you. SQL Server has a scripting feature like genDBC. Once you get your SQL Server database the way you want it, you can use this script to recreate it easily (where ever you want it).

A DSN does need to be created on each machine, but you can create one programmatically. The files section here has example(s).
Précédent
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform