Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations bkrike on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Access2000DB====>SQL2000
- Thread starter PerseusMi
- Start date
jimmythegeek
Programmer
Are you switching your back-end from Access to SQL Server, and staying with an Acess front-end?
If so, it's not as easy as it looks. There are two ways to do this.
1) Link to the SQL Server tables just like you do to Access tables.
First, every person that wants to use the system must have a dsn (control panel | ODBC Data Sources) that points to your SQL Server back-end.
Secod, Link Tables and select "ODBC Databases" as "Files of Type". Select your dsn and your set.
This is NOT the way I would suggest using SQL Server, because you are not allowing the server to do all of the processing for you, not to mention that I have run into trouble trying to update some tables and such using linked tables.
2) Unbind all your forms, and use ADO to populate all the forms on the fly. Advantge: This will increase your performance tremendously. Disadvantage: You have to basically rewrite all the code to use unbound forms and ADO. We did this on a pretty sophisticated medical application with nearly 100 tables, over 100 forms, etc. It took 2 developers a little over 2 months to modify all the code. But, the performance difference between an Access back-end and an unbound SQL Server back-end is like night and day.
I guess you could try it using the linked method, first, and if you get the results you are looking for, then so be it.
Hope this helps
Jim Lunde
compugeeks@hotmail.com
We all agree that your theory is crazy, but is it crazy enough?
If so, it's not as easy as it looks. There are two ways to do this.
1) Link to the SQL Server tables just like you do to Access tables.
First, every person that wants to use the system must have a dsn (control panel | ODBC Data Sources) that points to your SQL Server back-end.
Secod, Link Tables and select "ODBC Databases" as "Files of Type". Select your dsn and your set.
This is NOT the way I would suggest using SQL Server, because you are not allowing the server to do all of the processing for you, not to mention that I have run into trouble trying to update some tables and such using linked tables.
2) Unbind all your forms, and use ADO to populate all the forms on the fly. Advantge: This will increase your performance tremendously. Disadvantage: You have to basically rewrite all the code to use unbound forms and ADO. We did this on a pretty sophisticated medical application with nearly 100 tables, over 100 forms, etc. It took 2 developers a little over 2 months to modify all the code. But, the performance difference between an Access back-end and an unbound SQL Server back-end is like night and day.
I guess you could try it using the linked method, first, and if you get the results you are looking for, then so be it.
Hope this helps
Jim Lunde
compugeeks@hotmail.com
We all agree that your theory is crazy, but is it crazy enough?
- Status
Similar threads
- Locked
- Question