Some issues with FE and BE

[Tom]

Hi all,

I have a split db and I have some concerns,

1. when I open my db the link table manager is not available, if I craete
mde file and put it in the office how do I reconnect to the tables that on
the server?
2. I craeted a toolbar with the button backup database, when I use it, a
backup created for the FE, is there a way I can backup the BE from the FE?
3. I understand that the FE should be mde file on the stations and the BE on
the server:
A. do I just copy the BE to the server?
B. If I`ll put both FE and BE on the server and I`ll just create shortcut to
the desktops (without network drive letter), is that a good idea?

Please help me to clarify these issues,

Thanks for your help and time,

Tom

 

[Albert D.Kallal]

I have a split db and I have some concerns,

1. when I open my db the link table manager is not available

does the above problem exist for all databases, or just the one?

If you are using a2003, and the linked table manager is broken, there
solution is here

http://support.microsoft.com/kb/835519/en-us

I craete mde file and put it in the office how do I reconnect to the
tables that on the server?

Creating of a mde does not change the fact that you, (or you users) can
simply launch the linked table manager. You don't mention what version, but
even with a mde, you can simply go

Tools->Database Utilities->Linked Table manager

The fact of having a mde DOES NOT CHANGE this one bit.

Of course, why not link to the back end BEFORE you create the mde. Then,
when you distribute the mde to each user, it is already linked to the back
end? (no need to have users do this). Simply link you mdb to the back end.
Now, create the mde..the links will not be changed, and will remain in tact.

2. I craeted a toolbar with the button backup database, when I use it, a
backup created for the FE, is there a way I can backup the BE from the FE?

You will have to write code. Furhter, that code needs to take into a account
if other users are in the database. I simply use se the comapct and reaprt
(which also does a copy). So, compact and repair allows you to speify the
destication of the reusling compact. So, this is a ideal backup producres,
and if anyone else is in the file..then, you are not permissed to do this.

use

DBEngine.CompactDatabase strBackEnd, strToFile

You of course have to set strBackEnd, and strToFile to whatever you
want.....

Put the above is in a separate routing with some error trapping. If a error
occurs, then other users are in the database (or your current database has
some tables open...remember to close any form, or table that is open BEFORE
you attempt the above. Not a big deal if everything is not closed..but then
the above will simply error out.

3. I understand that the FE should be mde file on the stations and the BE
on the server:

Yes, correct

A. do I just copy the BE to the server?

Yes. You need to place it in a folder where all users have FULL permissions
to that shared folder (this includes create, and delete permissions).

B. If I`ll put both FE and BE on the server and I`ll just create shortcut
to the desktops (without network drive letter), is that a good idea?

No, it is bad idea. It is much less stable, and if one user has a problem in
the mde, then all users can come crashing down. You can imagine if word were
to freeze up, and everyone in the building would experience a freeze? It
makes no sense at all to attempt this kind of setup.

Please help me to clarify these issues,

I talk about all of the above issues in lenght at:

http://www.members.shaw.ca/AlbertKallal/Articles/split/index.htm

 

[Tom]

Albert,
Thank you very much.

Tom

does the above problem exist for all databases, or just the one?

If you are using a2003, and the linked table manager is broken, there
solution is here

http://support.microsoft.com/kb/835519/en-us


Creating of a mde does not change the fact that you, (or you users) can
simply launch the linked table manager. You don't mention what version,
but even with a mde, you can simply go

Tools->Database Utilities->Linked Table manager

The fact of having a mde DOES NOT CHANGE this one bit.

Of course, why not link to the back end BEFORE you create the mde. Then,
when you distribute the mde to each user, it is already linked to the back
end? (no need to have users do this). Simply link you mdb to the back end.
Now, create the mde..the links will not be changed, and will remain in
tact.


You will have to write code. Furhter, that code needs to take into a
account if other users are in the database. I simply use se the comapct
and reaprt (which also does a copy). So, compact and repair allows you to
speify the destication of the reusling compact. So, this is a ideal backup
producres, and if anyone else is in the file..then, you are not permissed
to do this.

use

DBEngine.CompactDatabase strBackEnd, strToFile

You of course have to set strBackEnd, and strToFile to whatever you
want.....

Put the above is in a separate routing with some error trapping. If a
error occurs, then other users are in the database (or your current
database has some tables open...remember to close any form, or table that
is open BEFORE you attempt the above. Not a big deal if everything is not
closed..but then the above will simply error out.



Yes, correct


Yes. You need to place it in a folder where all users have FULL
permissions to that shared folder (this includes create, and delete
permissions).



No, it is bad idea. It is much less stable, and if one user has a problem
in the mde, then all users can come crashing down. You can imagine if word
were to freeze up, and everyone in the building would experience a freeze?
It makes no sense at all to attempt this kind of setup.


I talk about all of the above issues in lenght at:

http://www.members.shaw.ca/AlbertKallal/Articles/split/index.htm

--
Albert D. Kallal (Access MVP)
Edmonton, Alberta Canada
(e-mail address removed)
http://www.members.shaw.ca/AlbertKallal

 

[Tom]

Albert,

If I create a n unbound form so the user can choose where to put the backup
file with a command button
that does: DBEngine.CompactDatabase strBackEnd, strToFile, is that going to
create problems?

Thanks,
Tom

 

[dbahooker]

as long as it's unbounds it's fine

you just don't want to open a table on the fe that lives on the
backend; that will mean that you won't be able to compact the backend


-Aaron

 

[Albert D.Kallal]

Albert,

If I create a n unbound form so the user can choose where to put the
backup file with a command button
that does: DBEngine.CompactDatabase strBackEnd, strToFile, is that going
to create problems?

Not a problem at all.

You could even popup the file dialog to browse to a location to save to....

You simply need to replace "strBackEnd" with the actual location of the back
end. strToFile is where you want the results...

You could even put in the forms expressions for those two values...

 

[dbahooker]

or if you don't like dealing with this tedium..

if you don't like making your end users wait 30 seconds to open their
databases-- then you could do something logical like keeping all your
friggin data in one place-- SQL Server.

Access Data Projects rock my world and you kids need to catch up to the
20th century.

YES; I LITERALLY MEAN THE 20th CENTURY.

I would rather use paper and pen than this stupid MDB crap.

-Aaron