jjrobert
2008-02-12 21:17:02 UTC
I apologize in advance for what will be a long question, but I have to think
there are others out there who are in the same boat and that you'll either
point me to a FAQ I've missed or give enough information in your reply to
help a bunch of us get past square one. Or maybe I'm at least at square 2.
OK, so I ran MSSA for Access to migrate an Access 2000 .mdb to SSE 2005,
told it I wanted to link tables and I got LOTS of errors for the queries -
most of which seems to have to do with append or update queries, ORDER BY,
etc.
Having read the FAQs and such, I'm not surprised by any of those errors. In
fact, after watching the Access 2003 Upsizing Wizard hang every time, I was
overjoyed to finally be getting somewhere.
But I'm terribly confused as to how to go about making the fixes. NOT what
the appropriate fixes are, but HOW and WHERE to make them.
And frankly, I'm still not sure what MSSA actually DID.
To put it another way, I think "if all goes well", my Access application is
supposed to function as before, except that the data will reside in SQL
Server (and things might be slower, need tuning, etc.)
When all goes not-so-well, though, I'm unclear as to whether I'm supposed to
edit the Access queries and try the migration again, or whether I'm just
supposed to edit the generated views in SSMA and apply the changes (or just
edit them directly in SSE in a tool like SQL Server Management Studio Express
or MS SQL Maestro).
The latter makes more sense, since the remedies proposed for most of the
errors seem to be things I can only DO in SSE. But having fiddled with some
of the views, I'm starting to wonder.
I sort of understand what linking the TABLES does, but what is MSSA actually
doing for each QUERY? When my Access application executes a query, is it
executing the original access query, or is it now somehow executing the "SSE
query" (or view, or whatever) that MSSA generated?
To try and answer this for myself, I edited one of the new views in SSE to
give a wrong answer, committed the change, and opened and ran my application.
I did not get the expected wrong answer, which leads me to believe that my
application might be running its same old query.
Is there a step in the migration that modifies my Access application to
point to the new views, and I'm just getting too many errors for SSMA to get
that far?
Is there something besides committing the change in SSE that I should be
doing before I run my Access application again?
Any and all help will be much appreciated.
-Jeff
there are others out there who are in the same boat and that you'll either
point me to a FAQ I've missed or give enough information in your reply to
help a bunch of us get past square one. Or maybe I'm at least at square 2.
OK, so I ran MSSA for Access to migrate an Access 2000 .mdb to SSE 2005,
told it I wanted to link tables and I got LOTS of errors for the queries -
most of which seems to have to do with append or update queries, ORDER BY,
etc.
Having read the FAQs and such, I'm not surprised by any of those errors. In
fact, after watching the Access 2003 Upsizing Wizard hang every time, I was
overjoyed to finally be getting somewhere.
But I'm terribly confused as to how to go about making the fixes. NOT what
the appropriate fixes are, but HOW and WHERE to make them.
And frankly, I'm still not sure what MSSA actually DID.
To put it another way, I think "if all goes well", my Access application is
supposed to function as before, except that the data will reside in SQL
Server (and things might be slower, need tuning, etc.)
When all goes not-so-well, though, I'm unclear as to whether I'm supposed to
edit the Access queries and try the migration again, or whether I'm just
supposed to edit the generated views in SSMA and apply the changes (or just
edit them directly in SSE in a tool like SQL Server Management Studio Express
or MS SQL Maestro).
The latter makes more sense, since the remedies proposed for most of the
errors seem to be things I can only DO in SSE. But having fiddled with some
of the views, I'm starting to wonder.
I sort of understand what linking the TABLES does, but what is MSSA actually
doing for each QUERY? When my Access application executes a query, is it
executing the original access query, or is it now somehow executing the "SSE
query" (or view, or whatever) that MSSA generated?
To try and answer this for myself, I edited one of the new views in SSE to
give a wrong answer, committed the change, and opened and ran my application.
I did not get the expected wrong answer, which leads me to believe that my
application might be running its same old query.
Is there a step in the migration that modifies my Access application to
point to the new views, and I'm just getting too many errors for SSMA to get
that far?
Is there something besides committing the change in SSE that I should be
doing before I run my Access application again?
Any and all help will be much appreciated.
-Jeff