ok...so you're saying it would be better just to use the unique timestamp as my unique identifier?
On Tue, Nov 18, 2008 at 8:00 AM, Joe Enos <[EMAIL PROTECTED]> wrote: > > If after all of this you still want to proceed, I'd suggest a two- > column primary key, with the userid being the first part, and a new > regular integer being the second part. You can store "lastentryid" or > "nextentryid" in an int column on the user table, then reference it > whenever you need to insert a record. > > I don't think you can both access and increment this column from > inside a function, so I think you'd either need to have your entire > statement inside of a stored proc, or use two separate commands. > > On Nov 17, 9:50 pm, BigJ <[EMAIL PROTECTED]> wrote: > > I see a formula section, but not sure how to go about it. I basically > > have an primary key called "EntryId" and I want to consist of UserId > > +unique counter, so if UserId="BigJ", and it's my first entry, then > > EntryId="BigJ1" and the next entry would be BigJ2 etc....any insight > > as to how to accomplish this? I know there is a formula field and I am > > looking into it, but any insight or simple examples are apreciated, as > > I left my SQL book at home lol...Thanks... >
