OK, that's an odd subject line. Let me try to explain what we have in our
table:

item language collectionID GUID
the form1 english 1 5
el form1 spanish 1 6
la form1 french 1 7
the form2 english 2 8
el form2 spanish 2 9
la form2 french 2 10

the collection ID is a way to group records into a 'set'. Now, normally, I'd
create another table called 'collections' and then relate that to this
table. So, to add a form, you'd first create a collection, then you could
add a form.

However, the developer I work with prefers this methodology of only having
one table, just to keep the number of tables and JOINS manageable (We have a
ton of tables...)

I'm trying to figure out if this is doable. The catch is making a new
collection ID and ensuring that it will be unique. I could obviously query
the DB by grabbing the top1 collectionID and then just increment it by one.
The catch is if two people are trying to add a new collection at the same
time. There's a chance that they'd both query the DB at the same time and
then attempt to make new, separate, collections, but then end up with them
sharing the same ID.

Is there a way to trigger a 'uniqueID' on a field like this on the SQL send
instead of first having to do a query look up and manually creating the
'unique' ID for this field?

Of is this just the wrong way to do it and go back to using multiple tables?

-Darrel