Planning the Form

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I am in the midst of creating a user input form and is link to a table. I
don't want the users to deal directly with the table itself. The user should
be able to view existing records and also add additional records. I am hoping
not to make my life to diffcult since I am not very knowleadge access
programmer and time restrictions. So my thoughts were is to set the form
initial for viewing the record table and then if the user wants to input he
can select a command append button. I assume I can store these values in a
query or separate table. The user can still view or change the records until
he exits the form; then the query or separate table will be added to the
existing table or replace information already recorded.

I guess I am looking for some input or suggestions on how I can make this
happen easily w/o a tremendous amount of effort.

Thanks
 
From what you are suggesting you want an unbound table and then add the input
data into the data table. You can use an Append Query where you reference the
fields on the form in the criteria line and then insert the data into the
table via a command button or some other control which has an event procedure
attached to it.
 
I am in the midst of creating a user input form and is link to a table. I
don't want the users to deal directly with the table itself. The user should
be able to view existing records and also add additional records. I am hoping
not to make my life to diffcult since I am not very knowleadge access
programmer and time restrictions. So my thoughts were is to set the form
initial for viewing the record table and then if the user wants to input he
can select a command append button. I assume I can store these values in a
query or separate table. The user can still view or change the records until
he exits the form; then the query or separate table will be added to the
existing table or replace information already recorded.

I guess I am looking for some input or suggestions on how I can make this
happen easily w/o a tremendous amount of effort.

Thanks
Click to expand...

What you're asking to do IS - in my opinion - excessive effort. Why
not simply use a bound form? The user can move to the new record using
the *> navigation button, or you can provide a button to do so; when
they enter a record and move off it, it will be automatically saved;
they'll be able to edit it freely up until that point.

Why the extra work of using a temp table? It can certainly be done -
but it a) usually isn't necessary and b) requires programming, while
the bound form requires no code at all.

John W. Vinson[MVP]
 
Back
Top