I am continuing my exploration about upsizing to SQLServer from Access
2000.
I have a split database with a front-end and a back-end, each of which
is A2K. I have spent some time in bookshops trying to learn about the
way forward and trying to decide which to buy. The bit I am interested
in is usually at page 900 and I am not sure whether I want to buy the
first 800.
It appears that upsizing creates an Access project as the front-end and
SQLServer as the back-end. Is it necessary for the front-end to be a
project instead of an .mdb (or .mde) file? What are the advantages and
the differences?
My front-end creates the links to the back-end by means of VBA code.
This means that if the back-end file is moved or I transfer a new
version of the front-end from my laptop to the client's system,
relinking is painless.
The actual tables are not all in a single .mdb file. The front-end
links most tables to one file but links a small number to a different
one. I'll not go into the reason why here.
If I use a project front-end can I link some tables to SQLServer and
some to an .mdb file? No there is another good reason why the second
lot cannot go into the SQLServer! I am trying to find out what it
possible.
The books usually seem to discuss upsizing an unsplit database. Do I
need to bring the tables back to the front-end before upsizing? or do
I simply upsize the back-end? If so, how does the front-end become a
project (that is, if it should)
Any guidance would be welcome.