"LilMorePlease" <LilMorePle***@discussions.microsoft.com> wrote in message
news:5A3537A7-32E7-4D10-B32F-0326F8CF65EA@microsoft.com...
> I've redesigned a database, properly normalizing it from 1 table to 8
> tables.
> I've spent a full month on this, building a full fledged application with
> custom functions and the whole nine yards.  The company I am working for
> is
> actually closing down their office and relocating across the nation, and
> the
> new database is going along with the move.  I won't be here to see the
> database being implemented at the new location, as I am leaving the
> company
> to start a new job.
>
> What can I do to maximize security so that the program doesn't "break"
> during the process of implementing it at the new location.  There will be
> one
> or two people who will be using the database (entering data, running
> reports
> etc).  I am wondering if it's a good idea to set up user accounts when I
> don't know any facts about who is going to be using the application (it
> hasn't even been determined yet).
>
> Ideas and suggestions are greatly appreciated!
>
> AA
>
>