A
Alan Z. Scharf
1. I have a form sorted by LastName, FirstName, bound to SQLServer view.
2. The underlying table has a primary key on ContactID (Identity) and an
index on LastName, FirstName.
3. The view underlying the form also is sorted on LastName, FirstName.
4. When the form requeries after an Insert via stored procedure, it visibly
goes back to the lowest ContactID Identity value, before going to newly
added record via: DoCmd.GoToRecord , , acLast.
5. Is there a way to prevent this flashing of the lowest Identity value
record before arriving at newly added record?
Either freezing the form, or some other approach?
Thanks very much.
Alan
2. The underlying table has a primary key on ContactID (Identity) and an
index on LastName, FirstName.
3. The view underlying the form also is sorted on LastName, FirstName.
4. When the form requeries after an Insert via stored procedure, it visibly
goes back to the lowest ContactID Identity value, before going to newly
added record via: DoCmd.GoToRecord , , acLast.
5. Is there a way to prevent this flashing of the lowest Identity value
record before arriving at newly added record?
Either freezing the form, or some other approach?
Thanks very much.
Alan