B
Bob Ryan
For years I have used autonumber fields as primary keys in
access database tables and I have used those tables as the
record source for the forms I create.
Many times I create subforms that link to the primary key
field or the control that is bound to the primary key.
This has always worked very well and easy.
An example would be an orders form that has a subform for
order details where the datasourse for the main form is an
orders table that has an autonumber field for a primary
key which links to the subform from that primary key.
I am doing my first access "project" as opposed to mdb
using a sqlserver back end and I find this method does not
work.
With the sqlserver back end the identity field does not
get updated till after you save the record which seems to
be too late to use the subform to add more detail
How do other get around this situation?
Thanks
access database tables and I have used those tables as the
record source for the forms I create.
Many times I create subforms that link to the primary key
field or the control that is bound to the primary key.
This has always worked very well and easy.
An example would be an orders form that has a subform for
order details where the datasourse for the main form is an
orders table that has an autonumber field for a primary
key which links to the subform from that primary key.
I am doing my first access "project" as opposed to mdb
using a sqlserver back end and I find this method does not
work.
With the sqlserver back end the identity field does not
get updated till after you save the record which seems to
be too late to use the subform to add more detail
How do other get around this situation?
Thanks