Upgrade to SQL server

  • Thread starter Thread starter Ginola
  • Start date Start date
G

Ginola

Hi,

I have few Access forms which works in the Access database. It does
not use MSDE or ADO in most of the functions. If I have to change the
Database from Access to SQL server, what things I have to change?
E.g. the form properties have the record source, how can I assign it
by codings ? I also use some queries to change the filter, and also
I have the Master and child relationship linking in the form, what do
I need to do??

Thanks, I am still struggling on the project.

Thanks
 
Ginola

An Access "front-end" can point to any number of sources of data, include
Access back-ends, SQL Server, ... As long as you've linked the front-end to
the SQL Server tables (and have the correct permissions set there), your
Access front-end should continue to work.

However, some of the queries that are easy for Access & its Jet database
engine to manage become more problematic when you connect to SQL Server
data. You will want (and may need) to inspect/test the operation of each
form and query, to ensure that performance hasn't suffered.

You haven't mentioned what problems you are having, so this is rather
general advice.
 
Do you mean using ODBC to link the sql server as database so that it
can pretend the tables in Access ?

I have used some codes like "CurrentDb.Execute", those codes have to
be changed, right ?
 
Ginola

Have you tried the code? (Yes, I created a DNS for ODBC so I could link to
SQL Server tables.)

SQL Server doesn't create an autonumber (ID) until after the record/row is
saved -- Access creates one when the first field is altered in a new row.
You may need to deal with this difference, too.
 
Sorry to read this message so late.

Does it mean this line of code
"CurrentDb.Execute"
will still work ??

The project has kind of change to use Access instead of SQL server,
but we want to use MSDE instead. Therefore, I can still use DSN, am I
right ??
 
Back
Top