any problem with 2003 mdb using sql 2005 tables linked ot another mdb?

  • Thread starter Thread starter Les Caudle
  • Start date Start date
L

Les Caudle

I've got a client who has several Access 2003 mdb's linked together.

My plan is to keep the reports in Access, but replace the front end forms with
C# and the Access tables with SQL 2005 tables.

So, the mdb would show the same tables, same table names, except they would
actually be SQL 2005 tables.

I'm curious if there would be any issues with linking the mdb's together (after
I'd migrated the table to 2005)?
 
Not sure what you mean by linking MDBs together. If the tables are in SQL
Server, the links would be between SQL Server and the MDB.

I'm curious, though, on what you expect to gain by recreating the forms in
C# and leaving the reports in Access.

--
--Roger Carlson
MS Access MVP
Access Database Samples: www.rogersaccesslibrary.com
Want answers to your Access questions in your Email?
Free subscription:
http://peach.ease.lsoft.com/scripts/wa.exe?SUBED1=ACCESS-L
 
Roger - with the forms in C#, the many users that connect to the database will
no longer have to open access over their network and deal with the data
corruption issues that have been occuring. (they recently brought me in about a
record that could not be deleted from the corrupt mdb).

I use custom .NET remoting code to communicate with the server, so the remote
users could be located anywhere on the Internet, and would work even with a
phone dialup connection.

The reports would be generated on the server, and display to the remote users as
snapfiles (I have a report screen that handles all this).

The remote users would no longer ever open an Access MDB file.

My guess is that all the mdb files that link to each other will be consolidated
anyway. I am unclear why there would need to be multiple mdb files.

Regards, Les Caudle
 
Back
Top