Passing Form Values - Deleting Duplicates

[sonoamore]

Ok, I've tried quite a few different code snippets now trying to make this work and it's giving me a small aneurysm.

2 Forms, 2 Tables

Goal:



- When button is clicked on FormA, open FormB with new record, setting the ID fields to the same value.
- If FormA's ID already exists in FormB's table, delete that record and start a new record with the ID set as described above.
- Copy values A,B,C from FormA to spots D,E,F in form B.

Basically what's occurring here is this:

FormA is the main data entry area. There is sometimes an additional form to generate (FormB) which includes some pieces of the data that already exist on FormA (nicknamed A,B,C in this case). However, if the user generates the form once and then later tries to do it again, I don't want to have multiple entries for FormB with the same ID. The ID is the distinguishing feature here as FormB's table setup is something like:

FORMB_ID ID A B C

This is so that each of the FormB records has a unique ID, and can be tied back to it's origin by use of the ID field.

Honestly starting to go a bit crazy, any help anyone can give is GREATLY appreciated!

[ItsMe]

I am pretty sure you can not get an aneurysm by doing something. Instead, it is something you are born with.

As for the A B C thing.... you have some issues with your tables. The design is what is causing your headache. This could cause problems if you do have an aneurysm.

The whole, creating forms thing, is very confusing. Users should be creating records. The application should dictate what tables the user will or will not create a record in. The developer of the application creates the relations. The relations allow for peace and serenity. You need to normalize your structure.

[sonoamore]

I am pretty sure you can not get an aneurysm by doing something. Instead, it is something you are born with.

As for the A B C thing.... you have some issues with your tables. The design is what is causing your headache. This could cause problems if you do have an aneurysm.

The whole, creating forms thing, is very confusing. Users should be creating records. The application should dictate what tables the user will or will not create a record in. The developer of the application creates the relations. The relations allow for peace and serenity. You need to normalize your structure.

Not sure why this response was even necessary.... but ok...

1. "A, B, C" FormA, FormB, etc, are just place holders for the real names of the fields, and tables, etc, since I can't post the actuals here.

2. No one's actually creating a form, it's an additional and seperate set of fields (or, a seperate form) that's not always necessary to fill out, but contains about 25% of the data that already exists. Hence why I want to copy it into that table. The application DOES dictate what tables they create records in, I just want to cut out some of the work by copying the data they've already entered.

3. I can't have duplicate entries in the table for FormB, so I'm hoping there is a way to check for an existing ID match and delete the record if it was alrady there.

Bonus: The term "have an aneurysm" is being used as a term to express frustration, much like "This thing is going to give me a heart attack!" If you were born with an aneurysm, you're probably dead.

[ItsMe]

Still confused. Not sure what to make of it. Sounds like you have multiple tables with duplicate data. Yet, you claim that you want to check for duplicate data.

[June7]

Aneurysm: swelling of blood vessel wall that weakens the vessel, like an over-stretched balloon that eventually bursts. Stress doesn't help and you will have a lot of stress with the db design you describe. I agree with ItsMe, design and the behavior of forms is confusing. Why is same data in two tables? Perhaps if you gave a full description of what this db is for and the table structure, we could better advise. If you want to attach db, follow instructions at bottom of my post.