Update Problem V2.2.1 Beta

J

John

Guest
I am getting an error on ALL updates made from the "show all records" screen using any update record icon.

When I select "show all", the database records are displayed correctly. When I click on the Update icon (adjacent to any record on the page)
DaDaBik displays the wrong record for update.
I turned on debug and sql display flags to see what was going on and to
verify I wasnt getting the "Limit" condition I saw in older Posts. It appears only the first column of the base table's compound primary key is being used
to construct the record to extract for update.
The select statement used to pull the record for update ignores all compound primary key columns after the first;
It is probably getting the first record from the table that matches the first primary key value.
My underlying table has 3 concatenated primary key columns.
(pkcol1,pkcol2,pkcol3)
Eg;
Debug Query to extract record for update is displayed like:
select col1,col2,coln from table where pkcol1 = 'somevalue'

Record extracted for update should be:
select col1,col2,coln from table where pkcol1='somevalue1'
and pkcol2 = 'somevalue2' and pkcol3 = 'somevalue3'

All other functionality is great!
I see new version is out, but "fixes map" doesn't talk about anything that might affect this.
Help is appreciated...
John
 
J

John

Guest
This is definetly a DaDaBik Bug..... Compound Primary Keys do not appear to be factored into the application.

I found a workaround for this:

1. Drop Base Table compound primary key
2. Alter Base table -> Create new auto incrementing INTEGER unique
Primary key column. I called mine Rec_key
3. Use DaDaBIK ADMIN Screen to "Refresh Table" due to newly added
column
4. Use DaDaBik Internal Table Manager to hide the new field from all the
screens. Even though it will appear on the Update screen!

Back in Business.... It works! and I didn't have to disturb any live data or the
MS Access Custom Front-End. You just have to be sure you can live with
the single column Primary key.

Hope This helps others....
Regards
John
 
E

Eugenio

Guest
John wrote:
>
> This is definetly a DaDaBik Bug..... Compound Primary Keys do
> not appear to be factored into the application.

Yes, at the moment DaDaBIK doesn't support multiple primary keys.

Eugenio.

(Latest version of DaDaBIK when this message was posted: 2.2.1)
 
J

JCL

Guest
Thank you so much, John - it does work, and I'm back in business too <smile>

JCL
 
Top