B
bdehning
Will splitting a database increase speed to open forms and reports over a network if tables are on the network and every user has every thing else?
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.
J
John Vinson
Will splitting a database increase speed to open forms and reports over a network if tables are on the network and every user has every thing else?
It will slow things down compared to each user having the entire
database on their desktop.
It will, however, provide MUCH better stability and (in many cases)
better performance than all users sharing an unsplit database. Such
sharing is pretty much sure to cause corruption and lockups.
B
bdehning
How can every user have the whole database on their computer and everyone able to view changes through a network?
Is this a dumb question?
Is this a dumb question?
T
Tony Toews
bdehning said:How can every user have the whole database on their computer and everyone able to view changes through a network?
Is this a dumb question?
Not at all. But just to make things a bit clearer.
Splitting means you create a front end containing the queries, forms,
reports, macros and modules. The tables and relationships are the
backend on the server. The FE is copied to each network users
computer. The FE MDB is linked to the tables in the back end MDB
which resides on a server. You make updates to the FE MDB and
distribute them to the users, likely as an MDE.
See the "Splitting your app into a front end and back end Tips" page
at http://www.granite.ab.ca/access/splitapp/ for more info. See the
Auto FE Updater downloads page
http://www.granite.ab.ca/access/autofe.htm 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
J
John Vinson
How can every user have the whole database on their computer and everyone able to view changes through a network?
Is this a dumb question?
No - it was a dumb (or incomplete at least) answer on my part!
The point to splitting the database is *not* to get better
performance. What I was intending to say is that it will give *worse*
performance, compared with the ideal of a local unshared database.
But the minor cost in performance is paid back with the ability to
share the same data among multiple users, and to avoid the corruption
and lockups caused by sharing a single unsplit database.
K
kerrpmb
There is no such thing as a database splitting. If on the copies you use
Microsoft Office Access you can put pictures, a copy of the paper you want on
the database, words, financials, and maybe even music. That is if you put
antoinette m. kerr in the access database. Ask it a question. There is no
additional programming so you can ask it a question about the database
itself. It can explain it to you using the instructions given it.
Microsoft Office Access you can put pictures, a copy of the paper you want on
the database, words, financials, and maybe even music. That is if you put
antoinette m. kerr in the access database. Ask it a question. There is no
additional programming so you can ask it a question about the database
itself. It can explain it to you using the instructions given it.
P
Pete D.
Yes!
kerrpmb said:There is no such thing as a database splitting. If on the copies you use
Microsoft Office Access you can put pictures, a copy of the paper you want
on
the database, words, financials, and maybe even music. That is if you put
antoinette m. kerr in the access database. Ask it a question. There is
no
additional programming so you can ask it a question about the database
itself. It can explain it to you using the instructions given it.
A
Arvin Meyer [MVP]
There most certainly is database splitting. I fact it is the only safe way
to run an Access/Jet database over a network, and the only way that you can
run an Access front-end connected to any other data source.
http://www.granite.ab.ca/access/splitapp/overview.htm
And to answer the OP, yes it is significantly faster because the entire
front-end does not need to be dragged over the network. Additionally, it is
safer because it significantly reduces the risk of corruption.
to run an Access/Jet database over a network, and the only way that you can
run an Access front-end connected to any other data source.
http://www.granite.ab.ca/access/splitapp/overview.htm
And to answer the OP, yes it is significantly faster because the entire
front-end does not need to be dragged over the network. Additionally, it is
safer because it significantly reduces the risk of corruption.
A
a a r o n . k e m p f
----------------------------------------------------------------------------------------
Access, however, is not perfect. Performance degrades significantly as
the database size increases. The database is also prone to corruption.
Finally, starting with an Access database has tempted many developers
to do a dangerous thing. Sometimes a single-user application becomes
popular enough that there's a desire for it to be used by multiple
simultaneous users. The temptation is to just move the Access database
file to a network share, copy the application to multiple machines,
and let many users connect simultaneously. Access performance drops
off quickly with multiple users, and it's highly unlikely that an
application that was designed for a single user will work reliably
with concurrent users.
http://msdn.microsoft.com/en-us/library/aa730870(VS.80).aspx
Access, however, is not perfect. Performance degrades significantly as
the database size increases. The database is also prone to corruption.
Finally, starting with an Access database has tempted many developers
to do a dangerous thing. Sometimes a single-user application becomes
popular enough that there's a desire for it to be used by multiple
simultaneous users. The temptation is to just move the Access database
file to a network share, copy the application to multiple machines,
and let many users connect simultaneously. Access performance drops
off quickly with multiple users, and it's highly unlikely that an
application that was designed for a single user will work reliably
with concurrent users.
http://msdn.microsoft.com/en-us/library/aa730870(VS.80).aspx
A
Arvin Meyer [MVP]
Once again you are trolling with misinformation. Once again your are
absolutely wrong on every count. You have never introduced even a shred of
proof to back up anything you post because that proof only exists in your
own mind.
The fact is the Access/JET functionality rivals any other database when both
are properly designed and sufficient network and machine resources are
applied.
The fact is that Access/JET performs well with hundreds of thousands, even
millions of records with properly designed and indexed tables.
The fact is that Access/JET performs well with 20 users, and I have had as
many as 53 users with 75 open applications running with any noticeable
performance problems.
If better security, or 24/7 operation, or high numbers of users, or more
than a GB of data is being used, a server based application is definitely
preferable. Your penchant for misinformation does a disservice to yourself,
and the community.
--
Arvin Meyer, MCP, MVP
http://www.datastrat.com
http://www.mvps.org/access
http://www.accessmvp.com
message
----------------------------------------------------------------------------------------
Access, however, is not perfect. Performance degrades significantly as
the database size increases. The database is also prone to corruption.
Finally, starting with an Access database has tempted many developers
to do a dangerous thing. Sometimes a single-user application becomes
popular enough that there's a desire for it to be used by multiple
simultaneous users. The temptation is to just move the Access database
file to a network share, copy the application to multiple machines,
and let many users connect simultaneously. Access performance drops
off quickly with multiple users, and it's highly unlikely that an
application that was designed for a single user will work reliably
with concurrent users.
http://msdn.microsoft.com/en-us/library/aa730870(VS.80).aspx
absolutely wrong on every count. You have never introduced even a shred of
proof to back up anything you post because that proof only exists in your
own mind.
The fact is the Access/JET functionality rivals any other database when both
are properly designed and sufficient network and machine resources are
applied.
The fact is that Access/JET performs well with hundreds of thousands, even
millions of records with properly designed and indexed tables.
The fact is that Access/JET performs well with 20 users, and I have had as
many as 53 users with 75 open applications running with any noticeable
performance problems.
If better security, or 24/7 operation, or high numbers of users, or more
than a GB of data is being used, a server based application is definitely
preferable. Your penchant for misinformation does a disservice to yourself,
and the community.
--
Arvin Meyer, MCP, MVP
http://www.datastrat.com
http://www.mvps.org/access
http://www.accessmvp.com
message
----------------------------------------------------------------------------------------
Access, however, is not perfect. Performance degrades significantly as
the database size increases. The database is also prone to corruption.
Finally, starting with an Access database has tempted many developers
to do a dangerous thing. Sometimes a single-user application becomes
popular enough that there's a desire for it to be used by multiple
simultaneous users. The temptation is to just move the Access database
file to a network share, copy the application to multiple machines,
and let many users connect simultaneously. Access performance drops
off quickly with multiple users, and it's highly unlikely that an
application that was designed for a single user will work reliably
with concurrent users.
http://msdn.microsoft.com/en-us/library/aa730870(VS.80).aspx
A
a a r o n . k e m p f
Jet can't handle a half dozen users and a mere 25mb of data.
it didn't work a decade ago, it doesn't work now.
Usability has gone _NOWHERE_ in the past decade.
Meanwhile, SQL Server is the worlds most popular database.
SQL Server is faster, easier, cheaper, more scalable, more stable,
more extensible, etc
More available.
EXCEL has more functionality than Access, and Excel works _GREAT_ for
1m rows!
it didn't work a decade ago, it doesn't work now.
Usability has gone _NOWHERE_ in the past decade.
Meanwhile, SQL Server is the worlds most popular database.
SQL Server is faster, easier, cheaper, more scalable, more stable,
more extensible, etc
More available.
EXCEL has more functionality than Access, and Excel works _GREAT_ for
1m rows!
T
Tony Toews [MVP]
"a a r o n . k e m p f @ g m a i l . c o m" <[email protected]>
wrote:
And that paragraph is exceedingly slanted and by someone who clearly
doesn't understand Access.
How many hours did it take you to find that paragraph?
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
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/
wrote:
And that paragraph is exceedingly slanted and by someone who clearly
doesn't understand Access.
How many hours did it take you to find that paragraph?
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
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/
T
Tony Toews [MVP]
Jet can't handle a half dozen users and a mere 25mb of data.
Wrong.
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
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/
A
a a r o n . k e m p f
Well you're the idiot that's stuck reccomending an obsolete database.
We're not the ones that are slanted-- YOU ARE.
JET IS OBSOLETE AND IT HAS BEEN FOR A DECADE.
-Aaron
We're not the ones that are slanted-- YOU ARE.
JET IS OBSOLETE AND IT HAS BEEN FOR A DECADE.
-Aaron
T
Troll Chaser
message
Well you're the idiot that's stuck reccomending an obsolete database.
We're not the ones that are slanted-- YOU ARE.
JET IS OBSOLETE AND IT HAS BEEN FOR A DECADE.
-Aaron
Off your meds again? We were hoping that your mommy was more careful about
reminding you.
Oh well, sorry that everyone has to put up with your immature behavior.
Perhaps, if you'd remember to take your medications, you might be useful
somewhere. I don't think they'll help you here in the computer world though
because it is quite obvious that you lack knowledge. I don't think they make
drugs for ignorance, but perhaps if you spend the next 15 or 20 years
studying, you might be able to actually post something useful.
Well you're the idiot that's stuck reccomending an obsolete database.
We're not the ones that are slanted-- YOU ARE.
JET IS OBSOLETE AND IT HAS BEEN FOR A DECADE.
-Aaron
Off your meds again? We were hoping that your mommy was more careful about
reminding you.
Oh well, sorry that everyone has to put up with your immature behavior.
Perhaps, if you'd remember to take your medications, you might be useful
somewhere. I don't think they'll help you here in the computer world though
because it is quite obvious that you lack knowledge. I don't think they make
drugs for ignorance, but perhaps if you spend the next 15 or 20 years
studying, you might be able to actually post something useful.
J
John W. Vinson
Oh well, sorry that everyone has to put up with your immature behavior.
Please don't compound the problem. What you're posting will not help Aaron,
the volunteers here, or the people coming to ask questions. Just ignore Aaron
or correct factual errors; personal attacks won't help.
T
Tony Toews [MVP]
John W. Vinson said:Please don't compound the problem. What you're posting will not help Aaron,
the volunteers here, or the people coming to ask questions. Just ignore Aaron
or correct factual errors; personal attacks won't help.
I agree.
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
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/
A
a a r o n . k e m p f
John;
you're the one that compounding the problem.
You sit there and spread lies-- and you accuse me of lying.
Go ahead and explain to everyone how ULS and Replication are still
available in Access 2007 (format), kid.
-Aaron
you're the one that compounding the problem.
You sit there and spread lies-- and you accuse me of lying.
Go ahead and explain to everyone how ULS and Replication are still
available in Access 2007 (format), kid.
-Aaron
J
John W. Vinson
Go ahead and explain to everyone how ULS and Replication are still
available in Access 2007 (format), kid.
They aren't, and I've never said that they were.