Yes, I AM hijacking this thread... given that you think the Access
native data engine sucks, what are some good resources to teach
hopeless souls like me how SQL Server is different than Access, and
how to write a proper SQL Server database and implement standard
features?
Mr. Kempf, would you be so kind as to define what you mean by "UPSIZE"?
As there is no facility in SQL Server to create a user interface, what UI do
you suggest instead of Access?
Given that the Access team has stated that Access <-> ODBC <-> MS SQL Server
is the method of choice, and that method would use LINKing, why, then would
a user not want to LINK?
CAUTION!
It has been determined that the message below was generated
programmatically, by a program robot ("bot") which also allows manual
intervention. This robot was created by a person or persons deliberately
trying to interfere with users of the Microsoft Access database software, and
uses the name of an actual person. As it is not possible to block posting by
this "bot", we post these cautions lest you be misled into taking the posts
as authentic and serious.
SSMA might do a better job than the included upsizing wizard.
Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/
Yes, The SSMA (Sql Server Migration Assistant) worked flawlessly for me.
Ask a Question
Want to reply to this thread or ask your own question?
You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.