Random databases

[tamaranth]

OK ...
Trying to import a set of new queries to an Access 97 database
Got message about 'Cancelled, as this would create a duplicate key'. (not running the queries, simply trying to import them -- and they're only select queries anyway).
Compact and repair database.
Same thing happens.
Compact and repair database, and swear.
Same thing happens.
EDIT: Delete Sacrifice a random innocent, virginal, white-robed query.
Import now fine ...

My database is demonically possessed.

Any other explanations?

Comments

[spride.livejournal.com]

The clue is in the string "Access 97"...

[tamaranth.livejournal.com]

believe me, at times like this I would ever so much rather be using something else. A Rolodex, for example.

[incy.livejournal.com]

youir databse was written by microsoft which according to some equates to your theory

[tamaranth.livejournal.com]

Funny you should mention that: from nisaba, earlier ...
demonically possessed PCs (http://www.theregister.co.uk/2000/03/10/us_preacher_finds_demonpossessed_pcs/) (with a link to the item about Bill Gates being the Devil)

Just a guess ...

[the-magician.livejournal.com]

... that the way MS stores queries is actually in a table of objects in the MDB and that for some reason, the unique ID for one of the imported queries matches a query you already have in the MDB, and that's the duplicate key it is complaining about.

Alternative guesses make even less sense:
e.g. one of the imported queries is an update query with a "run on import" flag that MS has never documented but which is trying to run when you import it.

One of the queries is some sort of "select and copy data" query which needs to build an output table to take the data and that table already exists so it won't allow that query to be added.

Re: Just a guess ...

[tamaranth.livejournal.com]

so, our options include:
1) A unique key that isn't
2) An update query that isn't
3) A can't-think-of-simple-summary.

I suspect (1) is closest: my considered theory* is that there was something Bad in a system table having to do with queries, and by deleting a random query I made that table notice that it was Bad, and fix itself.


*as opposed to opinion, which is that Access sucks