Access to SQL

  • Thread starter Thread starter Richard Choate
  • Start date Start date
R

Richard Choate

This weekend I used the Access wizard to convert a db to SQL server. There
were 2 choices, send tables to SQL or send whole thing to new SQL db. I was
experimenting so I sent the whole thing this time. I noticed that it
stripped out most of the forms in the process. Does it do that if it finds
incompatible code behind the form or what? I know this is an Access forum
but surely you know the answer.
Thanks,
Richard Choate
 
Hi,

I presume you mean the upsizing wizard. Usually Access
forms are coded using DAO that is not 100% compatible with
SQL server, unless you use linked tables and ODBC. ADO
provides the necessary tools to open a connection to SQL
server and manipulate data.

I have wasted plenty of time on the upsizing wizard with
some annoying bugs on Access 2000.

If you can get the tables and data into SQL the quickest
way around is to link the tables via ODBC, however it has
its limitations.

Hope this helps a little

Martin
 
I think it sucks that the whole form goes away. I think Access could strip
the code from the form without taking the form away. As you well know,
building forms is very tedious work. All of the sizing and placement can
take a long time. For that matter, Access should leave the code also and
quit trying to be so smart. A person might be able to doctor the code to
make it work without trashing *everything*. The code on a form is REALLY a
lot of work in many cases. I would try pretty hard to at least salvage
*some* of it. What do you think?
Richard

Hi,

I presume you mean the upsizing wizard. Usually Access
forms are coded using DAO that is not 100% compatible with
SQL server, unless you use linked tables and ODBC. ADO
provides the necessary tools to open a connection to SQL
server and manipulate data.

I have wasted plenty of time on the upsizing wizard with
some annoying bugs on Access 2000.

If you can get the tables and data into SQL the quickest
way around is to link the tables via ODBC, however it has
its limitations.

Hope this helps a little

Martin
 
Back
Top