Forms lose data -

bhecht

Registered User.
Local time
Today, 19:26
Joined
Apr 18, 2003
Messages
13
I have set up a system that allows a user to enter MS Access through Forms (Switchboard). Then the user can select to begin filling in their tax return, which is made up of several forms (Step 1 allows the user to go into Q1 & Q5, then continue on to Step 3 which then allows the user to select which forms to display in the next window consisting of Personal Details and Q10 AND/OR Q11)

The problems are:

1. When some forms are opened and then closed, they do not keep the data if reopened. How can i fix this?

2. How can I implement that Q1 (employment in Step 1) will allow the user to create several Employers, that are all linked to the one record in Step 1?

(I have uploaded the file onto http://www.btinternet.com/~dodo/boaz/project.zip in case that's helpful.
 
First, refresh the form before closing it. Perhaps a Me.Refresh in the form's close event.

Second, create a W2 (or employer table) table with a dual key; the userid and the W2 (or employer) ID. This way the user can have more than one W2 ( or employer).
 
It says i can't because a related record is required in table ...

Thank you for your reply. I tried the refresh answers, but it says

"you cannot add or change a record because a related record is required in table tbl_Step1"

How do i fix that?
 
It looks like you have a database design issue. You must be trying to add a child without having already added the potential parent. Orpans are not allowed in Access.
 
I am not sure how to fix that

I have looked at the relationships, and they appear right to me. But i have never done this before so i'm probably wrong.

How do i fix it?
 

Attachments

  • erd.jpg
    erd.jpg
    61.3 KB · Views: 160
1. Forms don't store data. Tables store data. If your form is not bound (has a query or table name in its recordsource) and its controls are not bound (have column names in the control's controlsource), there is no way to save data when the form is closed.

2. It is poor practice to name fields with only numbers.
 

Users who are viewing this thread

Back
Top Bottom