Insert record with composite key...

I use composite keys often (primary keys composed of two or more columns).

Using the Insert Record behavior, the tool requires a "Save inserted ID in Session".
I tested this and it saves a composite key session value of "0".
This doesn't matter as the composite key is made up of 'known' values.
Thus my point...why require the variable be set if it has no use in some instances?
Right now I am labeling these as NAname (NA as in not applicable)...but they muddy up my interface. I am in the process of wiring up table 5 of over 40...I don't want a mess of unusable variable floating around.

Am I missing something here, or can this requirement be removed...let the developer set the variable if they want it.

Thanks,
Brent

The ID Session will the tables Primary Key. It uses the mysql_insert_id() function to return the Primary key of the record that was just inserted. It sounds like your tables are not using a primary key, even when using a composite key, it is a good idea to use a primary key also.

I probably should have said "compound key" instead of "composite key"...however, same issue...same point.
Creating an auto-increment field in all tables is simply not good design. It is easier, but the integrity of the data will be upheld with the use of composite keys when ever possible.

It make no sense to require the variable if the developer won't use it.

99.99% of the people using Data Bridge create tables that use an auto increment ID in the table design.

Good grief man...shouldn't your software be open to all possibilities? The more modular it is the more powerful it will be.
This is simply, removing the requirement for the variable to be filled out (nothing more, nothing less)...this wouldn't screw anybody up or their legacy code.

I bought this software about a month ago...I am surprised you are not receptive to such a simple fix that furthers the robustness of the product.

Brent

I will put a feature request through.

Thank you!