|
|
Hi All,
From the original db.mdb, I will convert it to 2002-2003 format, then split
the database, then change it to .mde (I will be saving each step). I would
like to store the original db, convert format, and backend db in one secure
file. Then distribute the .mde to other employees. For the secure file, I
don't want other ppl to have access to it. should the .mde be able to obtain
the data from the tables in the backend db that is stored in the secure file?
Currently, I tried putting the original db, convert format, and backend db
(tables only) in a secure file. I stored the .mde in a completely different
file and drive, and my .mde doesn't work.
Any suggestions on how I can resolve this problem?
thanks in advance (much appreciated).
--
Learning
|
|
You are smart to save everything. Save your original MDB (unsplit) becuase
you can't go back and create it from an mde very easily. You didn't say if
you are running on a lan or not. If your FE is on each user's machine and the
MDE is on the lan, check to see that users have read/write/edit/ and delete
rights to the mde AND the folder it resides in.
"tracktraining" wrote:
[Quoted Text] > Hi All,
>
> From the original db.mdb, I will convert it to 2002-2003 format, then split
> the database, then change it to .mde (I will be saving each step). I would
> like to store the original db, convert format, and backend db in one secure
> file. Then distribute the .mde to other employees. For the secure file, I
> don't want other ppl to have access to it. should the .mde be able to obtain
> the data from the tables in the backend db that is stored in the secure file?
>
> Currently, I tried putting the original db, convert format, and backend db
> (tables only) in a secure file. I stored the .mde in a completely different
> file and drive, and my .mde doesn't work.
>
> Any suggestions on how I can resolve this problem?
>
> thanks in advance (much appreciated).
> --
> Learning
|
|
the secure file that stores the original mdb, convert mdb, mde and backend
mdb doesn't allow the user to write/edit/delete permission. the user will
have a shortcut to the mde file on their desktop. It seems like not allowing
the user permission to the file is cauzing the problem.
But then how do i make sure that the user only has access to the mde and not
the others (original, convert, and backend)? how should i set up the folder
permission level? or is there a different method?
Thanks,
Tracktraining
--
Learning
"Golfinray" wrote:
[Quoted Text] > You are smart to save everything. Save your original MDB (unsplit) becuase
> you can't go back and create it from an mde very easily. You didn't say if
> you are running on a lan or not. If your FE is on each user's machine and the
> MDE is on the lan, check to see that users have read/write/edit/ and delete
> rights to the mde AND the folder it resides in.
>
> "tracktraining" wrote:
>
> > Hi All,
> >
> > From the original db.mdb, I will convert it to 2002-2003 format, then split
> > the database, then change it to .mde (I will be saving each step). I would
> > like to store the original db, convert format, and backend db in one secure
> > file. Then distribute the .mde to other employees. For the secure file, I
> > don't want other ppl to have access to it. should the .mde be able to obtain
> > the data from the tables in the backend db that is stored in the secure file?
> >
> > Currently, I tried putting the original db, convert format, and backend db
> > (tables only) in a secure file. I stored the .mde in a completely different
> > file and drive, and my .mde doesn't work.
> >
> > Any suggestions on how I can resolve this problem?
> >
> > thanks in advance (much appreciated).
> > --
> > Learning
|
|
The users need to have Read/Write/Delete priveleges on the folder that
contains the BE in order to be able to use it. You should store the master
copy of the db (along with other files that you want to protect) in a
separate secure folder. You can store backup copies of the BE file in a secure
folder, in case something happens to the main be file, but there is not a lot
you can do to protect the main BE file. Any user with a little bit of
knowledge
could find your BE file and copy data from it, or otherwise do damage. If
you are worried about that, you may want to look into putting the BE on
a more secure application like SQL Server, if you have access to anything
like that.
Short of that, you should be sure to make frequent backups, which is often
done anyway as part of the regular backup routine for the server. You can
use a hidden form in your front end with a timer event to close the FE after
a certain time of day, in case someone doesn't close it before they leave for
day, which could prevent the BE from being backed up.
Another thing you are going to need to do is Compact and Repair the BE
every so often. How often depends on the frequency of use, number of
users etc., but after a while you (or the users) will notice a decrease in
speed of the db if a C&R hasn't been done recently. Some Access experts
say that you shouldn't do a C&R 'over the network'. In other words, you should
make a copy of the BE on your local hard drive, do the C&R on that, then
replace the network copy with that one. I don't know if this is absolutely
necessary, but that's how I always do it just to be safe.
--
_________
Sean Bailey
"tracktraining" wrote:
[Quoted Text] > the secure file that stores the original mdb, convert mdb, mde and backend
> mdb doesn't allow the user to write/edit/delete permission. the user will
> have a shortcut to the mde file on their desktop. It seems like not allowing
> the user permission to the file is cauzing the problem.
>
> But then how do i make sure that the user only has access to the mde and not
> the others (original, convert, and backend)? how should i set up the folder
> permission level? or is there a different method?
>
> Thanks,
> Tracktraining
>
> --
> Learning
>
>
> "Golfinray" wrote:
>
> > You are smart to save everything. Save your original MDB (unsplit) becuase
> > you can't go back and create it from an mde very easily. You didn't say if
> > you are running on a lan or not. If your FE is on each user's machine and the
> > MDE is on the lan, check to see that users have read/write/edit/ and delete
> > rights to the mde AND the folder it resides in.
> >
> > "tracktraining" wrote:
> >
> > > Hi All,
> > >
> > > From the original db.mdb, I will convert it to 2002-2003 format, then split
> > > the database, then change it to .mde (I will be saving each step). I would
> > > like to store the original db, convert format, and backend db in one secure
> > > file. Then distribute the .mde to other employees. For the secure file, I
> > > don't want other ppl to have access to it. should the .mde be able to obtain
> > > the data from the tables in the backend db that is stored in the secure file?
> > >
> > > Currently, I tried putting the original db, convert format, and backend db
> > > (tables only) in a secure file. I stored the .mde in a completely different
> > > file and drive, and my .mde doesn't work.
> > >
> > > Any suggestions on how I can resolve this problem?
> > >
> > > thanks in advance (much appreciated).
> > > --
> > > Learning
|
|
thanks. I think i know what to do now.
--
Learning
"Beetle" wrote:
[Quoted Text] > The users need to have Read/Write/Delete priveleges on the folder that
> contains the BE in order to be able to use it. You should store the master
> copy of the db (along with other files that you want to protect) in a
> separate secure folder. You can store backup copies of the BE file in a secure
> folder, in case something happens to the main be file, but there is not a lot
> you can do to protect the main BE file. Any user with a little bit of
> knowledge
> could find your BE file and copy data from it, or otherwise do damage. If
> you are worried about that, you may want to look into putting the BE on
> a more secure application like SQL Server, if you have access to anything
> like that.
>
> Short of that, you should be sure to make frequent backups, which is often
> done anyway as part of the regular backup routine for the server. You can
> use a hidden form in your front end with a timer event to close the FE after
> a certain time of day, in case someone doesn't close it before they leave for
> day, which could prevent the BE from being backed up.
>
> Another thing you are going to need to do is Compact and Repair the BE
> every so often. How often depends on the frequency of use, number of
> users etc., but after a while you (or the users) will notice a decrease in
> speed of the db if a C&R hasn't been done recently. Some Access experts
> say that you shouldn't do a C&R 'over the network'. In other words, you should
> make a copy of the BE on your local hard drive, do the C&R on that, then
> replace the network copy with that one. I don't know if this is absolutely
> necessary, but that's how I always do it just to be safe.
>
> --
> _________
>
> Sean Bailey
>
>
> "tracktraining" wrote:
>
> > the secure file that stores the original mdb, convert mdb, mde and backend
> > mdb doesn't allow the user to write/edit/delete permission. the user will
> > have a shortcut to the mde file on their desktop. It seems like not allowing
> > the user permission to the file is cauzing the problem.
> >
> > But then how do i make sure that the user only has access to the mde and not
> > the others (original, convert, and backend)? how should i set up the folder
> > permission level? or is there a different method?
> >
> > Thanks,
> > Tracktraining
> >
> > --
> > Learning
> >
> >
> > "Golfinray" wrote:
> >
> > > You are smart to save everything. Save your original MDB (unsplit) becuase
> > > you can't go back and create it from an mde very easily. You didn't say if
> > > you are running on a lan or not. If your FE is on each user's machine and the
> > > MDE is on the lan, check to see that users have read/write/edit/ and delete
> > > rights to the mde AND the folder it resides in.
> > >
> > > "tracktraining" wrote:
> > >
> > > > Hi All,
> > > >
> > > > From the original db.mdb, I will convert it to 2002-2003 format, then split
> > > > the database, then change it to .mde (I will be saving each step). I would
> > > > like to store the original db, convert format, and backend db in one secure
> > > > file. Then distribute the .mde to other employees. For the secure file, I
> > > > don't want other ppl to have access to it. should the .mde be able to obtain
> > > > the data from the tables in the backend db that is stored in the secure file?
> > > >
> > > > Currently, I tried putting the original db, convert format, and backend db
> > > > (tables only) in a secure file. I stored the .mde in a completely different
> > > > file and drive, and my .mde doesn't work.
> > > >
> > > > Any suggestions on how I can resolve this problem?
> > > >
> > > > thanks in advance (much appreciated).
> > > > --
> > > > Learning
|
|
|