Unknown error message

[CleoMan]

I use SQL statements in my code to generate cetain values required in my reports, and I have written a piece of code that worked fine a couple of months ago.

Now I'm testing all code and all of a sudden I get this error I have never seen before:

"Name not unique in this context" and gives the name of the table as well as other names of tables restemp.db which I do not know about.

Does anyone have a idea as to what the message means or just simply put: what is going on?

Any help help or avdice is appreciated.

 

[footpad]

Cleoman,

It's certainly an interesting error and most certainly one generated by BDE. There's very little information available about it and, without more details of what's happening in your application at that point, it's hard to say precisely what is going on.

In any event, it is a BDE error message and the fact that it used to work suggests corruption of some form. I'd start by
verifying that your %TEMP% and Private directories are emptied of all BDE objects, include 0-byte .REM files.

Also, try manually deleting and recreating the indexes associated with the original table. Indexes can be comrrupt, just like tables, and it's hard to detect corrupted indexes. (This is, FWIW, why older versions of Table Repair deleted them out of hand.)

If that doesn't help, carefully review your code and verify the indexes and data of all tables involved in the process. (I recall a nortoriously time-consuming problem that ended up being caused by an unlinked lookup table tacked onto a form's data model.)

ResTemp.db itself is a BDE temporary table, though it appears that Borland hasn't documented its purpose publically (results temp? resource temp? who knows?). If memory serves, it usually appears as a query or filter result.

Finally, you should use care to avoid excessively long path or table names. While I've not seen any specifics on this, I have seen isolated reports or problems. Personally, I still avoid using LFN's in my applications--primarily because I still work with users running Windows 95/OSR2. *Shrug*

Hope this helps...

-- Lance

 

[CleoMan]

I hoped that it would be a simpler problem, but alas.
Thanks Lance, I'll try to get this problem sorted out with your help.

Let you know if it works, thanks for your time