Hi,

I am upgrading an application (kind of source safe app) and some of the
tables are named like this: USERS, PROJECTS, FILES, HISTORY, LABELS.

Any worries?


TIA,
Lucian

Lucian


Apart from getting yourself confused you mean The system tables are in a different database so they won't be interfered with by yours. However, to stop confusing yourself I suggest you try and avoid using names that are used for the system files eg I renamed my Users table to Staff.

Roy Lambert [Team Elevate]

> so they won't be interfered with

I heard stuff like this before I hope it really stays like that.


> avoid using names that are used for the system files eg I renamed my
> Users table to Staff.

Funny thing, at the office we have a table called "setup" for users. I
dislike that and for my own apps I don't actually want to call "Users"
anything else than "Users", because it's actually storing users (not
staff like in your case, maybe).

I'd rather like the system tables being called in such a manner so that
they'll never interfere with my stuff, for example "$sys$_users" ...
but I guess it's too late for that now .


--
Thanks,
Lucian

Lucian,

<< I am upgrading an application (kind of source safe app) and some of the
tables are named like this: USERS, PROJECTS, FILES, HISTORY, LABELS. >>

No.  The SQL parsing is always contextual and related to the current
database, so you shouldn't have any problem naming the tables anything that
you want.

--
Tim Young
Elevate Software
www.elevatesoft.com

> No.  The SQL parsing is always contextual and related to the current
> database, so you shouldn't have any problem naming the tables
> anything that you want.


Allrightieeee!

--
Thx,
Lucian