Splitting a Access 2007 database question

[Bob H]

I have a mdb type databse which I intend to convert back to accdb and then
split it to FE and BE. Then I will install the FE on local computers,
leaving the BE on the company server.

My question is, if a user opens the FE form and edits data, will that data
be updated on or into the BE tables so that anyone else who opens the FE
form will immediately see the edited/updated data.
Otherwise if that is not the case then I'll have to leave things as they
are.

Thanks

 

[Albert D. Kallal]

I have a mdb type databse which I intend to convert back to accdb and then
split it to FE and BE. Then I will install the FE on local computers,
leaving the BE on the company server.

My question is, if a user opens the FE form and edits data, will that data
be updated on or into the BE tables so that anyone else who opens the FE
form will immediately see the edited/updated data.

Nothing changes in this regards. In other words, if you did not split, and
allowed multiple users into the application, or split, the results are
exactly the same. So, when users update data, that data is updated.
Splitting does not change this.

 

[Bob H]

Ok, thanks for the reply, but I feel I need to be a bit more specific here.
The FE of the database which I intend to install on local computers are
laptops which will be taken away to specific locations in the UK. In 1/2
cases the laptop is not able to make a connect with the company server,
so in that case that is where my concern is, in that if data is added or
edited will it stil be updated on other computers?

Thanks

 

[Albert D. Kallal]

Ok, thanks for the reply, but I feel I need to be a bit more specific
here.
The FE of the database which I intend to install on local computers are
laptops which will be taken away to specific locations in the UK. In 1/2
cases the laptop is not able to make a connect with the company server,

Ok, however, if the data base is split, or not split, how would the above
change? If you have the data sitting in a shared folder on your server,
then if users can't access that folder when they are on the road, then they
can't access that folder on the road! (really very simple here!!).

so in that case that is where my concern is, in that if data is added or
edited will it stil be updated on other computers?

You don't have any data in the front end part. That front end part is ONLY
the application part. Think of installing word on your computer, but the
documents (data) are still placed in that shared folder. If you can't
access that folder, then you can't use the data in that folder can you?

Splitting has ZERO effect on the above scenario. If you planning to give
those laptops THEIR OWN copy of the data, then when they modify that data,
you have to come up with a means to share that data with others, and that
not
easy. Again, splitting fixes none of this problem. Splitting does not change
this problem in ANY WAY what so ever.

think of the problem in terms of the system not being split..the results of
your issues is EXACTLY THE SAME IN BOTH cases....

If you need sharing of data, then consider SharePoint, or some of the
solutions pointed out in the folwling article of mine:

http://www.members.shaw.ca/AlbertKallal//Wan/Wans.html

SharePoint might be the most easy solution since you can sign up for free
office live and not have to pay to "set up" the infrastructure needed to
share table data. And, it free for the 1st 50megs of data...more then enough
for most applications..

Read the above article first, but if you interested in sharePoint, then here
some info:

http://blogs.msdn.com:80/access/arc...egrating-with-office-live-small-business.aspx