>
> Well, I didn't expected such a reaction to my idea!
>
> My generator is not a primary key. What I am trying to do is the
> following.
>
> I am migrating an application which originally used DBF tables
> and used a lot of temporary tables. I know this is is not a good
> practice but to accelerate the migration, now in the new version
> I'm developping in FireBird, I'm using a temporary database in
> the server and every client PC creates its temporary tables there
> (I first tried using the temporary database locally in the client
> PC but I can't use fbembed because I need more than one
> application to access the same database). Each instance of the
> application, when it starts, gets the number of the generator and
> names its tables in the temporary database using this number as
> an identifier followed by a "_" and correlative numbers. As there
> are many temporary tables and there may be a lot of users during
> the day but no user during the night, what I wanted to do was
> that the first that starts the application in a new day resets
> the generator and so the generator wont increase forever. I know
> 2 ^ 31 is a big number but anywa
> y I wanted to to prevent...
>
> I also thought using another identifier but the user may be
> duplicated and the PC name too. I consider there may occur that
> an instance of the application didn't finalize normally and some
> temporary tables remain in the temporary database and so there
> may be conflict between the tables of an instance and the tables
> created by the same PC the day before if there is some that
> wasn't deleted.
>
> May be my idea is a bit foolish, but anyway... is there a way to do this?
>
> Gustavo

if noone is using the databases at night, then wouldn't it be easier just to
run a batch file of ISQL scripts which is scheduled at night?
Alan