Database corruption

  • Thread starter Thread starter Evi
  • Start date Start date
E

Evi

A database I have used for some time has developed a very strange problem.
It contains details about Opera CDs with a table which contains the Operas,
another which contains the recordings and another the Record Labels.

(there are other tables but these are the main ones)
The tables all have autonumber primary key field and the Recordings table
has its Primary key RecID, OperaID from the Opera table, LabelID from the
labels table.

I have a form based on the recording table. A combo box based on the
recording table uses RecordsetClone to find the Recording I want. It
contains RecID, Opera Name and Label Name.

For all the other records it works: if I want to find the recording of
Madama Butterfly on the Frequenz label it will find that, not the same opera
on the Europa label. But for 1 set, the behaviour is different. When I try
to find a particular recording of I Due Foscari, it takes me to the first
recording in the combo. Yet the two recordings have different RecID fields.
I've tried the database Repair and importing into a new database and even
deleting and re-inserting the records. I deliberately put another recording
between them yet the problem persists.

I created a new combo box and even another form based on the Recording table
but the results were the same.

I've put the database on my website on the Opera page on my website at
--
http://homepage.ntlworld.com/evwool/

If you want to see this phenomena at work, open either FrmRecAndTracks or
FrmRecAndSing and try using the combo box to turn to Due Foscari on the
Memories label. You will see that it turns only to that opera on the Myto
label. Try turning to other operas with multiple recordings and you will see
that they work correctly.

I fear that there is no cure but wonder if anyone has had a similar
experience.
Evi
 
If you have event code for a combo box (I am guessing, or assuming you do!),
then you should turn off autocorrect.

With AutoCorrect, some characters like the letter "i" etc can cause the
combo box to do weird things.

Assuming that all other entries work, and even other entries with duplicates
work, then likely the autocorrect feature is causing trouble.

In the other tab of the combo box, try setting the autocorrect feature to
"no". You should do this for most combos.

Give that try, and see what happens....

You can also try reading the KB article that mentions using autocorrect on a
combo can cause problems:

http://support.microsoft.com/?id=165480

The above may not be your problem...but you should give it a try.

I don't believe you have a corrupted data base.
 
You are an absolute star, Albert! You have saved me hours of wasted effort
recreating the whole database. I turned off Autocorrect for the combos and
sure enough, all is working as it should. Thank you.
Evi
 
Back
Top