Okay, here's the problem. I have a database that I'm am manipulating
through VB5 (MDB created in Access 97). I have several data controls on the
form; one is for the main record, and the others are used for DBCombo boxes.
I have a New command button which fires the <Data
control>.Recordset.AddNew method. This works fine. I also have a Save
button, which fires a <Data control>.Recordset.Update method (the various
text boxes on the form are bound to the main data control). It saves the
record, just as it's supposed to.
However, it's HOW the record is saved that is killing me!! For some
explain, the database is being designed to track PC hardware configurations.Quote:>BIZARRE< reason, this dumb thing is overwriting existing records! To
The primary key in the PC table is a PC number field. Right now, there are
10 records in the table, numbered 1 through 10, sequentially (no, I'm not
using an AutoNumber field). When I click the New button to generate PC 11,
and then save the record, I can go back to Access and see that the PCs have
been renumbered to run 2 through 11, inclusive! Furthermore, there are no
new records; there are still only 10 records in the table!
The data control opens the table as a dynaset, if that's relevant. I
can add records in Access just fine, and they all stay there. Can somebody
This is happening on both a stock VB5 Enterprise and an SP3 machine, so
don't suggest SP installation. Is it something in my code?