Upsizing to SQL Server - process timing changes

[John]

I upsized a database to SQL Server using the upsizing wizard. Having done
this I discovered that the sequence of events have changed. Previously, as
soon as a field was entered fields were filled in, such as calculated fields
in queries and autonumber fields, defaults, etc.. Now that the database is
upsized, nothing is filled in until the, it seems I go off of the record
(i.e. just moving forward or back). I need these fields avaiable to perform
other macros? Anyone have this issues, or a solution to this problem?

John R

 

[Brendan Reynolds]

SQL Server is not Jet. It behaves differently in some respects, and what
you're seeing with Identity fields is one of those differences. With Jet,
the AutoNumber field is updated as soon as the new record is 'dirtied' (i.e.
as soon as you begin to type into any bound control) but with SQL Server, it
is not updated until the record is saved. That's the way SQL Server is
designed, and you can't change it.

Although it would be nice, it just isn't realistic to expect to be able to
run the upsizing wizard and have everything work the way you're used to. Any
non-trivial application is likely to require some modification after the
conversion. In your example, any code that requires the value of the
Identify field will need to be modified to save the record first.

--
Brendan Reynolds (MVP)
http://brenreyn.blogspot.com

The spammers and script-kiddies have succeeded in making it impossible for
me to use a real e-mail address in public newsgroups. E-mail replies to
this post will be deleted without being read. Any e-mail claiming to be
from brenreyn at indigo dot ie that is not digitally signed by me with a
GlobalSign digital certificate is a forgery and should be deleted without
being read. Follow-up questions should in general be posted to the
newsgroup, but if you have a good reason to send me e-mail, you'll find
a useable e-mail address at the URL above.