Hi!

TomDill (or TomasDill) is my Nickname there. I do not hide self and my real name is in my messages there.

Correct, there might be a lot of problems related to multiple databases and free tables. We solved this problem by maintaining the same IDs table for all databases and it was a part of our data dictionaly (something like SDT). In other our applications we used different names for each different database and diferent function name for different database. Indeed tyhis have a lot of solutions. Just take the general idea, and extend it ...



>>Hi!
>>
>>If you're interested, the way of doing it for VFP datatbase is described in FAQ article at the www.tek-tips.com site. We used the approach described there for years without any conflicts, but with some restrictions that are described in that FAQ article too.
>>
>
>Are you using a pseudonym (?? - spelling) there? Hi, Tom :)
>
>You FAQ How to organize auto-increment key field in VFP?
>faq184-259 has few minor problems... First of all, you need to ensure, that the NextID table is opened for the correct database. We had situations using code like yours, when incorrect NextID table was opened. So, I added a check for this into our lNextID function...
>
>>>Hi all,
>>>
>>>If you are interesting for a generation primary key problem, you can read an article "The easy way to form a primary key" at http://www.geocities.com/vhpcg/primkey.html
>>>
>>>Best regards,
>>>Vladimir Trukhin