Using a Form

[BigO56]

Hello Everyone,

I am currently working within Access 2013. I am running into a problem and I would like to see if is possible to have a form when changes are made to existing records within the form, the changed records will be reflected into another table, and the existing record will stay the same.

[zmbd]

+ It's doable; however, not something I would advise.
My approach would be to instance a second database to hold the temporary table that has a copy of the current records.
From there you Bind the form to this secondary backend as its record source.
Now unless you copy the changed records back from the secondary backend any changes will either be lost if the secondary backend is deleted or you need to develop some method to handle either these secondary backend or to copy the changed record back to the primary data tables.

+ If you would provide more detail there might be a better solution to your issue.

[BigO56]

Thanks for the response zmbd. My goal is to keep the database as simple as possible for the users and I think having two different databases will cause confusion between the users. To solve this problem I have been trying to use an append query between the original table and the appended table, and in the form the appended table is a subform.

Original Table
ID Autonumber (PK)

one to many

Appended Table
ID Autonumber (PK)
Original table ID Number (FK)

But when I try to run the query I continue to get "0 fields to Null due to a type conversion failure, key violations etc." is there any way to work around this?

Thank you for your help, I hope I provided enough detail.

[PhilOfWalton]

It sound to me as if the OP needs a transaction database with the form showing the fist record ??????????

Don't seem logical to me, but with no detail who can tell?

Phil

[zmbd]

Exactly Phil, not enough detail.
Until and unless OP can tell us exactly what the goal is here then we're just guessing...
The transactional method is a good approach and one I use against my data as I don't use the cascade-delete in my relations between tables so it's very handy to be able to roll-back the changes if one of the records somewhere cannot be altered.

BigO56,
A) The secondary backend is only to hold a temp table, the user wouldn't even be aware of its existence if handled properly.

B) perhaps you can provide the needed details?
As you can see, we now have two viewpoints on what it is that you are attempting, is it:
1) You are attempting to preserve the original data
or
2) You are attempting to validate changes before committing/saving them to the records.
or
3) Something else?

C) Please review our FAQ on how to ask a good question:
How to ask "good" questions --
You have the "Brevity" aspect down; however, your posts are lacking the needed "Technical Details." IN this case IMHO, you need to provide us with the concept behind this data manipulation.

D) You should also read:
home > topics > microsoft access / vba > insights > database normalization and table structures
From the two posts here, it gives me the impression that there is a basic design flaw.

++ It would be helpful to know how experienced you are with Access, VBA, and database design.