Hello,
We have an Access application that we are considering moving to a CS DB
(maybe SQL Server) for performance reasons. We are just in the
preparatory,
information-gather stage. Keep in mind that I am not a database
developer;
I understand the broad concepts but few of the details.
This is not your usual DB application. The users, who work in a
consulting
firm, get data from each of their clients each year and must massage it
into
shape for use with other applications. Each database is unique, with a
different set of fields tailored for that case, and is single-user. The
processing is mostly canned (via code in a system MDE) but the users do
sometimes work directly with the data using native Access.
The ideal solution is to move the data out of Access but minimize the
changes to the existing Access programming (forms, re****ts, SQL, and so
forth) and also allow users to continue to work in Access directly. We
would also like to make the location of the data an option: e.g., use the
CS
DB in the office, but if they need to work at home or on the road allow
them
to copy the data to a local MDB and back. Or a local version of the CS
DB?
So I'm looking for any and all ideas for doing this or links to useful
information. ODBC seems an obvious place to start. E.g., replacing the
data tables with links to the CS tables. Can it be as simple as that?
(Are there more suitable newsgroups for these questions?)
TIA,
Jim
|
