The Database Split Controversy

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

It seems like everyone has a different opinion on whether or not to split a
database.

Is there a good website reference which goes through the pros and cons of
doing this? I come from a MS SQL server / MySQL background, it seems like
NOT splitting is a poor idea. People who I've spoken to are adamant that
splitting is the *worst* possible thing you could do.

It seems however that so long as you keep a persistant connection open over
the network, or keep the FE / BE on the same machine you are probably ok.

Any thought, arguments, /gripes?

thanks,
-David
 
I've never seen anyone indicate that splitting is a BAD idea, just that it
may not be necessary in some limited instances. All the previous posts I
have found from MVPs indicate that you should split the database, but you
can get away with not doing it if you have only one or two users and don't
need to modify the structure often. All the posts I found leaned toward
splitting.

Who are you talking to?
 
DBG said:
It seems like everyone has a different opinion on whether or not to
split a database.

Is there a good website reference which goes through the pros and
cons of doing this? I come from a MS SQL server / MySQL background,
it seems like NOT splitting is a poor idea. People who I've spoken
to are adamant that splitting is the *worst* possible thing you could
do. [snip]
Click to expand...

What "people" were these? I suggest never asking them any Access related
questions ever again.

There are circumstances where one might argue that splitting is not
*necessary*. Anyone who would argue that will actually cause a problem are
just ignorant of the facts.
 
It seems like everyone has a different opinion on whether or not to split a
database.
Click to expand...

I have seen VERY few arguments for running a multiuser database
unsplit.
Is there a good website reference which goes through the pros and cons of
doing this? I come from a MS SQL server / MySQL background, it seems like
NOT splitting is a poor idea. People who I've spoken to are adamant that
splitting is the *worst* possible thing you could do.
Click to expand...

Who are these people!? They're certainly not posting to this
newsgroup! If you're using SQL/Server or MySQL, you are ipso facto
"splitting" (the data is on the server, the user interface is on the
desktop); splitting Access just replicates this structure.
It seems however that so long as you keep a persistant connection open over
the network, or keep the FE / BE on the same machine you are probably ok.
Click to expand...

The one point againt splitting is that a split database REQUIRES a
fast, solid, reliable network; Access is more sensitive than most
programs to network hiccups. Splitting over a WAN or over a wireless
network is going to be a problem. But IME a split database on a LAN is
*the* way to go; and sharing an unsplit database among multiple users
is a sure route to bloating, bad performance, and database corruption.

John W. Vinson[MVP]
 
or keep the FE / BE on the same machine you are probably ok.

Seems to me that having both on the same machine sort of negates the purpose
of splitting.

Multiple users using a shared BE (data only) but each with their own local
copy of the FE (forms, reports, queries). Multiple users using the same FE
is a primary source of corruption, that's why they each get their own local
copy. Having forms, reports, queries local also reduces network traffic.
Having a "shared" FE on a network drive sort of defeats both purposes. I
suppose it might be ok for a lightly used app.
People who I've spoken to are adamant that
splitting is the *worst* possible thing you could do.
Click to expand...

These are experienced Access developers? Are they using the same definition
of splitting? Hard to believe...

HTH,
 
George Nicholson said:
Seems to me that having both on the same machine sort of negates the purpose
of splitting.
Click to expand...

The reason being to facilitate upgrades to the program. Replacing the front
end without needing to mess with the data.

-David
 
Thanks all, I am now convinced that splutting is the way to go.
Click to expand...

<gasp>
<shudder>

No! No! Don't ever splut your database...

<bg>

Splitting however is a Good Thing.

John W. Vinson[MVP]
 
lol. Sometimes I want to splut my computer with a baseball bat :)

My database I will split :>

-David
 
Back
Top