By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
446,398 Members | 982 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 446,398 IT Pros & Developers. It's quick & easy.

Splitting an Access database

P: n/a
Hi,

I have a database that I created in Access 97 and then converted to 2000.
Its running along but after looking here I believe more by good luck than
good management. I do not know any code and have created it by looking at
how Northwind works.

My problem is that I've been asked to set it up for more users (4 or 5).

I gather I need to split it into front end/back end and put the data (back
end) on the server with the forms, queries and reports (front end) on each
users workstation. Apparently there are different versions of Access
running on the workstations eg 2000, 2002 and 2003. Could someone please
tell me if this is going to cause a problem. Should I have the same version
on each workstation.

Thanking you in advance.
--
Christa
Nov 13 '05 #1
Share this Question
Share on Google+
5 Replies


P: n/a
"Christa Waggett" <3w****@ispdr.net.au> wrote in message
news:11***************@stitch.ispdr.net.au...
Hi,

My problem is that I've been asked to set it up for more users (4 or 5).

I gather I need to split it into front end/back end and put the data (back
end) on the server with the forms, queries and reports (front end) on each
users workstation.
Correct.
Apparently there are different versions of Access
running on the workstations eg 2000, 2002 and 2003. Could someone please
tell me if this is going to cause a problem. Should I have the same
version
on each workstation.

That would be the ideal solution although you can save into previous version
from A2003. You'd have an obvious management overhead if you plumped for
the multi-version option.

Regards,
Keith.
www.keithwilby.com
Nov 13 '05 #2

P: n/a
Christa Waggett wrote:
Apparently there are different
versions of Access running on the workstations eg 2000, 2002 and
2003. Could someone please tell me if this is going to cause a
problem.


Not besides additional work for U. U just need the backend to be in the
lowest version (2000)

Beware of any temporary user-specific tables though. They should be
created/used in the frontend. Not the backend.

/jim
Nov 13 '05 #3

P: n/a
Di
I use 3 front ends, one for each version and a backend in the oldest
version ie 2000. I also use code to make sure that my databases are all
pointing to the same backend.

I have had crashing and database bloating problems when sharing across
versions especially those that I have converted from 97.

NB!!! - backup before they start sharing.

D...
Jim Andersen wrote:
Christa Waggett wrote:
Apparently there are different
versions of Access running on the workstations eg 2000, 2002 and
2003. Could someone please tell me if this is going to cause a
problem.
Not besides additional work for U. U just need the backend to be in

the lowest version (2000)

Beware of any temporary user-specific tables though. They should be
created/used in the frontend. Not the backend.

/jim


Nov 13 '05 #4

P: n/a
Br
In news:11*********************@l41g2000cwc.googlegro ups.com,
Di <di************@bpb-na.com> said:
I use 3 front ends, one for each version and a backend in the oldest
version ie 2000.
Why not just use A2000 since 2002/2003 still support the 2000 format?
I also use code to make sure that my databases are
all pointing to the same backend.

I have had crashing and database bloating problems when sharing across
versions especially those that I have converted from 97.
Yes, always better to import objects into a new database :)
NB!!! - backup before they start sharing.


Br@dley
Nov 13 '05 #5

P: n/a
Thank you for all your advice. I've managed to split it and it looks okay
and have connected the front end application using the linking via the
toolbar. I imagine using code to make sure they all point in the right
direction would be better but I do not know how.

Thanks again,

Christa

"Br@dley" <n0****@4u.com> wrote in message
news:Mc******************@news-server.bigpond.net.au...
In news:11*********************@l41g2000cwc.googlegro ups.com,
Di <di************@bpb-na.com> said:
I use 3 front ends, one for each version and a backend in the oldest
version ie 2000.


Why not just use A2000 since 2002/2003 still support the 2000 format?
I also use code to make sure that my databases are
all pointing to the same backend.

I have had crashing and database bloating problems when sharing across
versions especially those that I have converted from 97.


Yes, always better to import objects into a new database :)
NB!!! - backup before they start sharing.


Br@dley

Nov 13 '05 #6

This discussion thread is closed

Replies have been disabled for this discussion.