multiple tables

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Pierre - 23 Apr 2005 18:40 GMT

Hi all,

i have a netwok application that read tables in 3 different mdb files.

Would it be a good idea for the network load to put all the table in
one mdb files instead of three.

Best regards,
Pierre

Reply to this Message

Tim Ferguson - 23 Apr 2005 20:22 GMT

"Pierre" <pf@arobas.net> wrote in news:sNvae.6032$3%4.1230448
@weber.videotron.net:

> Would it be a good idea for the network load to put all the table in
> one mdb files instead of three.

It's not really a question about network loads, it's about application
integrity. If the three tables are related -- in other words, if there are
rules that constrain what can happen to one table depending on the contents
of another table -- then they _have_ to be in the same mdb file.

As a second point, if you are even slightly worried about your network
capacity or efficienc, then just don't use mdb sharing. Move straight onto
MSDE. Jet sharing is highly susceptible to network problems and time-outs
or even a rogue NIC somewhere else on the network can corrupt an mdb file.

Hope that helps

Tim F

Reply to this Message

Jesper Fjølner - 24 Apr 2005 14:49 GMT

> As a second point, if you are even slightly worried about your network
> capacity or efficienc, then just don't use mdb sharing. Move straight onto
> MSDE. Jet sharing is highly susceptible to network problems and time-outs
> or even a rogue NIC somewhere else on the network can corrupt an mdb file.

What's a NIC?

Reply to this Message

Rick Brandt - 24 Apr 2005 15:05 GMT

>> As a second point, if you are even slightly worried about your network
>> capacity or efficienc, then just don't use mdb sharing. Move straight onto
>> MSDE. Jet sharing is highly susceptible to network problems and time-outs
>> or even a rogue NIC somewhere else on the network can corrupt an mdb file.
>
> What's a NIC?

Network card.

One of the few pieces of computer hardware that can "work poorly". By that I
mean that most hardware either works or it doesn't. NICs can work less than
optimally and many programs wouldn't care other than performance. Access is a
bit of a canary in the coal mine for this area. A poorly working NIC will
usually butcher an Access file in short order.

Signature

I don't check the Email account attached
to this message. Send instead to...
RBrandt at Hunter dot com

Reply to this Message

Tim Ferguson - 24 Apr 2005 15:26 GMT

"Rick Brandt" <rickbrandt2@hotmail.com> wrote in news:7JNae.23$461.13
@newssvr11.news.prodigy.com:

Like he said,

> A poorly working NIC will
> usually butcher an Access file in short order.

... wherever it is on the network; even if it's not directly involved in
the Access application at all...

B Wishes

Tim F

Reply to this Message