T
terri
I have a data-bound continuous form that “flattens†three tables into a
spreadsheet-like view. Part of the primary key for table 1 is the text for
cat; the table 2 key includes cat and type; table 3 includes cat and type and
action -- not my design, but it cannot be changed.
Tbl1 Tbl2 Tbl3
Row1: Cat1 Type1 action1
Row2: Cat2 TypeA action1
Row3: Cat2 TypeA action2
Row4: Cat2 TypeB action1
Row5: Cat3 Type2 action1
If the text of Cat2 or TypeA in any row is edited, after the save the other
rows will be correctly updated via cascading updates, but not before the
Write Conflict (Save Record) message is responded to. I understand that
multiple records in the underlying recordset are being affected, but as long
as the cascade is successful I don’t care -- I just don’t want the user to
have to constantly respond to this message.
I haven’t gleaned anything from other threads addressing this dialog that
applies when the update isn’t made via a programmatic SQL call but with a
data-bound form.
Any ideas?
spreadsheet-like view. Part of the primary key for table 1 is the text for
cat; the table 2 key includes cat and type; table 3 includes cat and type and
action -- not my design, but it cannot be changed.
Tbl1 Tbl2 Tbl3
Row1: Cat1 Type1 action1
Row2: Cat2 TypeA action1
Row3: Cat2 TypeA action2
Row4: Cat2 TypeB action1
Row5: Cat3 Type2 action1
If the text of Cat2 or TypeA in any row is edited, after the save the other
rows will be correctly updated via cascading updates, but not before the
Write Conflict (Save Record) message is responded to. I understand that
multiple records in the underlying recordset are being affected, but as long
as the cascade is successful I don’t care -- I just don’t want the user to
have to constantly respond to this message.
I haven’t gleaned anything from other threads addressing this dialog that
applies when the update isn’t made via a programmatic SQL call but with a
data-bound form.
Any ideas?