Networking

L

LJ

I would like to know if any one can instruct me on how to slip my file in
two...to be able to place it on a network...i know if i put the file as is in
the network it will slow down it performace drastically...

Any ideas

Thank you
LJ
 
A

a a r o n _ k e m p f

Access does not work well on a network.
Get over it.

Move to SQL Server
 
D

Duane Hookom

I have created lots of working Access applications running on networks with
the back-end on a shared network drive and the front-end on a local hard
drive. There is a splitter wizard available in Tools->Database Utilities.

I usually do this manually by creating a new, blank front-end and then
importing all the objects other than tables into the new MDB. Use File->Get
External Data to link to the tables in the original database.
 
A

a a r o n _ k e m p f

Whatever Pete

I fire on all thrusters-- I just don't stalk people-- run around
writing complaints to my ISP because I have the audacity to _SWEAR_
about something I believe in.

I'm so sorry that you're a wuss and you don't know how to evaluate
whether SQL Server is the best solution for you-- I urge you to take a
class on SQL Server in order to learn the 'worlds most popular
database'.

It says so at www.microsoft.com/sql

I would stop talking shit and start staying focused-- Access runs like
crap over half the networks.. and it doesn't run on the other half.
Just because your cry baby database does not work-- does that make it
MY FAULT?
 
S

So Sorry For Poor Aaron

Poor, poor pitiful aaron.

He gets so lonesome for Big Bruce, Big Bubba, and Big Barney that he just
can't resist trolling to try to get himself re-incarcerated. They don't even
mind if he rants about SQL Server. They just think he's so cute in an orange
jumpsuit, or out of it.

aaron, all three "Big" brothers say, "Smoochie, smoochie, we can't wait for
you to come back, sweetie."

But, you know what? aaron knows well that Access works well on a LAN. He
just hates Access and the people who support it.

Pity Poor Aaron
 
L

LJ

Thank you very much for your help fellas...

Duane Hookom said:
I have created lots of working Access applications running on networks with
the back-end on a shared network drive and the front-end on a local hard
drive. There is a splitter wizard available in Tools->Database Utilities.

I usually do this manually by creating a new, blank front-end and then
importing all the objects other than tables into the new MDB. Use File->Get
External Data to link to the tables in the original database.
Click to expand...
 
Top