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

Split database

P: n/a

Due to problems with corruption of database I have splitted this
database (MS Access 2000) on back end (usage for myself, tables and
data) and front end (usage for users, tables are linked
here,forms,reports etc.).

This has helped me to increase a bit safety of the system.

However,I thought that I will be able to work on design of forms in back
end database but is is not possible when people are working in front
end.

So I had to make a another copy of front end with tables linked to back
end in order to be able to develop things.

I have a very strong feeling that this is not a best way how to do it.Am
I mistaken?

Oskar

*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!
Nov 12 '05 #1
Share this Question
Share on Google+
3 Replies


P: n/a

"oskar hritz" <os*********@sca.com> skrev i melding
news:40***********************@news.frii.net...

Due to problems with corruption of database I have splitted this
database (MS Access 2000) on back end (usage for myself, tables and
data) and front end (usage for users, tables are linked
here,forms,reports etc.).

This has helped me to increase a bit safety of the system.

However,I thought that I will be able to work on design of forms in back
end database but is is not possible when people are working in front
end.

So I had to make a another copy of front end with tables linked to back
end in order to be able to develop things.

I have a very strong feeling that this is not a best way how to do it.Am
I mistaken?

Oskar

Work on a copy of the frontend, and switch when ready.

Sigurd
Nov 12 '05 #2

P: n/a
Oskar-

That sounds like exactly the RIGHT way to do it. You don't want to work on
the back end. That should just hold your tables and basically data that gets
changed regularly by users and that all users need to know about. Your front
end should be for forms and queries, maybe temporary tables that are results
of queries. Basically, objects that aren't updated frequently or don't need
to be shared with all users.

For development work, I would suggest you have a separate copy of both the
front and back end database. It's surprisingly easy to delete or damage
large amounts of records when you're developing your system. And you don't
need absolutely current data to test your forms, queries and modules. Just a
sample with large enough tables to truly test the speed and ease of use.

Mike Metzger

Nov 12 '05 #3

P: n/a
oskar hritz <os*********@sca.com> wrote:
Due to problems with corruption of database I have splitted this
database (MS Access 2000) on back end (usage for myself, tables and
data) and front end (usage for users, tables are linked
here,forms,reports etc.).
Good.
However,I thought that I will be able to work on design of forms in back
end database but is is not possible when people are working in front
end.

So I had to make a another copy of front end with tables linked to back
end in order to be able to develop things.

I have a very strong feeling that this is not a best way how to do it.Am
I mistaken?


As Sigurd and Mike have stated this is the best way to do things.

See the "Splitting your app into a front end and back end Tips" page at my website
for more info. See the Auto FE Updater downloads page at my website to make this
relatively painless.. It also supports Terminal Server/Citrix quite nicely.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Nov 12 '05 #4

This discussion thread is closed

Replies have been disabled for this discussion.