|
-
Nov 4th, 2000, 11:03 AM
#1
Thread Starter
Lively Member
Is there a database backend that I could use that is more robust than Access JET before moving to SQL. I have a very large program that uses DAO and moving it to ADO will take a long time! I would like to use an interim backend if possible.
The problems I am experencing are to do mostly with database size restrictions rather than performance issues although a healthy dose of speed from using ADO with SQL will not go un-noticed.
Thanks
-
Nov 4th, 2000, 01:17 PM
#2
Lively Member
You *Should* be able to migrate the tables directly to SQL/Server and th only change in your program should be to change the connection type from dbJet to dbODBC, and then the connection string. DAO was always intended to ork with ODBC as well as Access. In 90% of cases this works; but you cannot guarantee evry time.
If you have a problem, post your connection code for the dbEngine etc. and I will try to modifu for you. (PS: I also need to know the SQL database name and the name of the server on which it will reside.
-
Nov 7th, 2000, 02:27 PM
#3
Thread Starter
Lively Member
Thanks for the reply.
In essence, this is the general connection string
DIM DB As DAO.Database
DIM RS As DAO.Recordset
SET DB = Opendatabase("\databasepath")
SET RS = DB.Openrecordset("SQL Statement")
This is used 100's of times through out the program with many varying SQL statements to numerous tables. I believe my biggest problem may be to convert the SQL statments....I think.
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|