Error message

[MWinAZ]

Opening my database and trying to open 1 table I get an error message sayng "The changes you requested to the table were not successful because they would create duplicates values in the index, primary key, or relationship........" & then the next error message says "the Visual Basic for Applications project in the database is corrupt".


Any & all suggestions are greatly appreciated!!

[CJ_London]

have you tried compacting?
have you tried decompiling/re compiling?
do you have front end/back end?

[MWinAZ]

Disclaimer: I'm a novice at best & building a db for my business because nothing in the market seems to fit.....so feel free to talk to me like a 3rd grader :-)
I have tried compacting and get the same error message. Not sure how to respond to your 2 other questions but THX SO MUCH FOR RESPONDING!!

[CJ_London]

if you are using visual basic code then try decompile/recompile - this will remove any old code which might be causeing the corruption.

To do this, follow post#4 of this link

http://www.access-programmers.co.uk/...ight=decompile

A backend contains your tables only, a front end contains your queries, forms, reports and modules and uses linked tables to the back end. One of the benefits of doing this is that you do not lose access to your data if the front end becomes corrupted (although you can still get data corruptions). If you are not structured like this at the moment, I would do so.

Easiest way is to create a new db (called say backend) and click the external data tab>access and follow the prompts to import all your tables from your existing db. Then close the backend, and reopen the front end. Delete all your tables and do almost the same as before -click the external data tab>access and follow the prompts to link all your tables. Job done

[NTC]

well given your self proclaimed novice status I will hazard the guess that you made a field 'required' in your table - during table design; and then now that you are playing around with it your are forgetting to put in a value in that field.....or possibility you set a field as Indexed = Yes, No Duplicates and are either leaving it empty which is a no no or are duplicating a value......

this really shouldn't fire just on the opening of the table itself - but maybe your description is not exactly precise - in any case I would look for those field properties and clear them out.....