W
wazza_c12
Hi There
Last (simple) database I created I had the main entry form unbound, so
that a user hit an "add entry" button, and an isert query was called...
This avoided records being written until user had put all details in a
form and decided to add it.
I'm now embarking on a more complex relational database project and
fear if I go the same path as before it may cause issues like I am
unable to access what the autonumber primary key is of a record that
was just inserted etc.
Would that be a problem? Is there an easier way to go about all this?
If I have a bound form, and halfway through filling it out the user
decides they dont want to do that operation anymore .... how does one
go about canning a half entered record?
Cheers
Warwick
Last (simple) database I created I had the main entry form unbound, so
that a user hit an "add entry" button, and an isert query was called...
This avoided records being written until user had put all details in a
form and decided to add it.
I'm now embarking on a more complex relational database project and
fear if I go the same path as before it may cause issues like I am
unable to access what the autonumber primary key is of a record that
was just inserted etc.
Would that be a problem? Is there an easier way to go about all this?
If I have a bound form, and halfway through filling it out the user
decides they dont want to do that operation anymore .... how does one
go about canning a half entered record?
Cheers
Warwick