L
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
P
Pete D.
More info needed. Normally you you split the datafile into front end and
back end and have fun but you really don't provide much information here.
Could also just give them a link to the file.
back end and have fun but you really don't provide much information here.
Could also just give them a link to the file.
J
John W. Vinson/MVP
On Sun, 27 Jul 2008 14:35:58 -0700, Lori
It's considered polite to post a more detailed question in the big
textbox, not just the subject line. You're talking to human
volunteers, not to a search engine.
Access is multiuser out of the box. You have to go to a bit of extra
effort (e.g. opening the database with the Exclusive option) to force
it to be singleuser.
Please post back with the Access version, how your network is set up,
and some more details about the problem you're having. Also see
http://www.granite.ab.ca/access/splitapp.htm for suggestions on how to
properly "split" a database so it can be shared without causing bloat,
performance problems and corruption.
It's considered polite to post a more detailed question in the big
textbox, not just the subject line. You're talking to human
volunteers, not to a search engine.
Access is multiuser out of the box. You have to go to a bit of extra
effort (e.g. opening the database with the Exclusive option) to force
it to be singleuser.
Please post back with the Access version, how your network is set up,
and some more details about the problem you're having. Also see
http://www.granite.ab.ca/access/splitapp.htm for suggestions on how to
properly "split" a database so it can be shared without causing bloat,
performance problems and corruption.
A
a a r o n _ k e m p f
Access does not work well with multiple users.
it is reccomend for everyone - from beginners to experts- move to SQL
Server for these reasons:
a) performance
b) future-proofing
c) reliability
d) ease of administration
SQL Server is self-tuning.
Access doesn't support (consistently) more than a single user and a
single record.
it is reccomend for everyone - from beginners to experts- move to SQL
Server for these reasons:
a) performance
b) future-proofing
c) reliability
d) ease of administration
SQL Server is self-tuning.
Access doesn't support (consistently) more than a single user and a
single record.
B
Bob Larson
Here's another link to help too:
http://members.shaw.ca/AlbertKallal/Articles/split/index.htm
--
Thanks,
Bob Larson
Access MVP
Administrator, Access World Forums
Utter Access VIP
Free Access Tutorials and Resources: http://www.btabdevelopment.com
http://members.shaw.ca/AlbertKallal/Articles/split/index.htm
--
Thanks,
Bob Larson
Access MVP
Administrator, Access World Forums
Utter Access VIP
Free Access Tutorials and Resources: http://www.btabdevelopment.com
S
So Sorry For Poor Aaron
"a a r o n _ k e m p f" (aka Kempf The Troll, aka Aaron the Jailbird, aka
Doesn't for aaron, maybe, because if you don't know what you're doing, you
can screw anything up pretty badly. I'll bet aaron can screw it up so badly
it won't work at all, without half trying, because he's demonstrated over and
over that he knows less than nothing about Access.
But, even for people who aren't experts, it works well for several tens of
concurrent users, and for people with the right needs, who know what they are
doing, works very nicely with over two hundred users.
Take aaron's advice and you'll be paying through the nose for a two-hundred
user database application... got that, aaron, cutie?... through the nose.
The only ones who'd make such a sweeping recommendation are aaron and his
sweethearts, Big Bruce, Big Bubba, and Big Barney. None of the four of them
know anything about Access.
And, lest we forget, expensive, requiring a CAL for each user, and so "easy
to administer" you need to have a professionally-trained DBA (which you don't
with a split Access-Jet or Access-ACCDB database). And, for reasonably-sized
databases, the kind Access is used with, normally, none of the above may be
true.
Must be Christmas-time. All I can hear from the vast audience who know more
than aaron does is "Ho, ho, ho!" SQL Server is "self-tuning" just as much as
COBOL was "self-documenting".
The Cutie in the Orange Jumpsuit is on the list for a re-recording session,
so he can entertain the Big brothers with something other than "switch to SQL
Server" or a brain transplant so he can post more than one single phrase.
He's the poster boy for "One-Track Minds", but, alas, it's not concentration,
it's a lack of capacity and reasoning ability.
But Big Bruce, Big Bubba, and Big Barney don't care about his _mind_!
Poor, poor, pitiful aaron.
Cutie said:Access does not work well with multiple users.
Doesn't for aaron, maybe, because if you don't know what you're doing, you
can screw anything up pretty badly. I'll bet aaron can screw it up so badly
it won't work at all, without half trying, because he's demonstrated over and
over that he knows less than nothing about Access.
But, even for people who aren't experts, it works well for several tens of
concurrent users, and for people with the right needs, who know what they are
doing, works very nicely with over two hundred users.
Take aaron's advice and you'll be paying through the nose for a two-hundred
user database application... got that, aaron, cutie?... through the nose.
it is reccomend for everyone - from beginners to
experts- move to SQL Server for these reasons:
The only ones who'd make such a sweeping recommendation are aaron and his
sweethearts, Big Bruce, Big Bubba, and Big Barney. None of the four of them
know anything about Access.
a) performance
b) future-proofing
c) reliability
d) ease of administration
And, lest we forget, expensive, requiring a CAL for each user, and so "easy
to administer" you need to have a professionally-trained DBA (which you don't
with a split Access-Jet or Access-ACCDB database). And, for reasonably-sized
databases, the kind Access is used with, normally, none of the above may be
true.
SQL Server is self-tuning.
Must be Christmas-time. All I can hear from the vast audience who know more
than aaron does is "Ho, ho, ho!" SQL Server is "self-tuning" just as much as
COBOL was "self-documenting".
Access doesn't support (consistently) more than
a single user and a single record.
The Cutie in the Orange Jumpsuit is on the list for a re-recording session,
so he can entertain the Big brothers with something other than "switch to SQL
Server" or a brain transplant so he can post more than one single phrase.
He's the poster boy for "One-Track Minds", but, alas, it's not concentration,
it's a lack of capacity and reasoning ability.
But Big Bruce, Big Bubba, and Big Barney don't care about his _mind_!
Poor, poor, pitiful aaron.
A
a a r o n _ k e m p f
a CAL for each user? ?
AS IF
what decade do you think that this is?
SQL Server has been free for a decade. If you don't know it by now--
you can sign up to take a class on SQL Server licensing for all I
care.
www.microsoft.com/sql
SQL Server Express supports quad core processor without any CALs...
and it's free.
200 users in a database.. uh.. still free!
nice try, kid.. but really- you should wake up and smell the coffee
-Aaron
AS IF
what decade do you think that this is?
SQL Server has been free for a decade. If you don't know it by now--
you can sign up to take a class on SQL Server licensing for all I
care.
www.microsoft.com/sql
SQL Server Express supports quad core processor without any CALs...
and it's free.
200 users in a database.. uh.. still free!
nice try, kid.. but really- you should wake up and smell the coffee
-Aaron
A
a a r o n _ k e m p f
SQL Server is self-tuning
Select * From Sys.Missing_Index_Details
you really should step up and learn it yourself
Database Tuning Advisor and Profiler?
It just cannot be beat!!
Oh, but that might cost $49/seat (for the developers edition).
If you're not worth $49 piece of software, then you shouldn't be using
databases.
Of course, you're not using databases.. you're using a glorified
spreadsheet.
Except excel supports single user activity without crapping out.
Select * From Sys.Missing_Index_Details
you really should step up and learn it yourself
Database Tuning Advisor and Profiler?
It just cannot be beat!!
Oh, but that might cost $49/seat (for the developers edition).
If you're not worth $49 piece of software, then you shouldn't be using
databases.
Of course, you're not using databases.. you're using a glorified
spreadsheet.
Except excel supports single user activity without crapping out.