OT: MS Access Blank Title 59758

Yahoo Archive
1
It is designed for small groups and depends on excellent network
connection. 12 users will work fine unless your network is spotty. That
will lead to corruption and having to constantly get everyone out so
you can run the repair utility on the datafile.

It's better if you do a split design and put the tables in one file and
then put queries and forms in another file that you distribute to each
PC. Check help for Linked table if you are not familiar with this.

If you outgrow the limits you can migrate the data tables to SQL server
and then change the linked tables. This works very well. To prepare for
that possiblity use sql server naming rules for the table and field
names. Don't put space characters in the names PartTable is better that
Part Table in Sql server.

--- In vantage@yahoogroups.com, "dupuismd" <mdupuis@...> wrote:
>
> Hello group
> I have an off topic kind of question. What are the pro's/Cons of
> building a MS Access database and putting it on a server for use by a
> dozen clients? I have in the past heard of problems with record
> locking and data corruption. I have seen an Access data base lock up
> requiring frequent rebuilds. This again is old history, has anything
> changed with this product?
>
> TIA
> Mark
>
2
Hello group
I have an off topic kind of question. What are the pro's/Cons of
building a MS Access database and putting it on a server for use by a
dozen clients? I have in the past heard of problems with record
locking and data corruption. I have seen an Access data base lock up
requiring frequent rebuilds. This again is old history, has anything
changed with this product?

TIA
Mark
3
Mark,



If you start dumping in data using access you could corrupt or not
maintain the data integrity in Vantage. Only through using the vantage
application can this be maintained 100%.



If you want to use access for reporting, no updates, you might be
alright but this is why crystal reports is there. I hope this helps.



Dale Kalsow | Information Technologies Director
____________________________________________________________________
Determan Brownie, Inc. | 1241 72nd Avenue NE | Minneapolis, MN 55432

* Phone: (763) 502-9689 | * Fax: (763) 571-1789

* dale.r.kalsow@... | * http://determan.com/



"Ambition is the path to success. Persistence is the vehicle you arrive
in."



Electronic Privacy Notice. This e-mail, and any attachments, contains
information that is, or may be, covered by the Electronic Communications
Privacy Act, 18 U.S.C. 2510-2521, and is also confidential and
proprietary in nature. If you are not the intended recipient, please be
advised that you are legally prohibited from retaining, using, copying,
distributing, or otherwise disclosing this information in any manner.
Instead, please reply to the sender that you have received this
communication in error, and then immediately delete it. Thank you in
advance for your cooperation.

________________________________

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of dupuismd
Sent: Monday, October 08, 2007 2:55 PM
To: vantage@yahoogroups.com
Subject: [Vantage] OT: MS Access



Hello group
I have an off topic kind of question. What are the pro's/Cons of
building a MS Access database and putting it on a server for use by a
dozen clients? I have in the past heard of problems with record
locking and data corruption. I have seen an Access data base lock up
requiring frequent rebuilds. This again is old history, has anything
changed with this product?

TIA
Mark





[Non-text portions of this message have been removed]
4
Actually this database will have nothing to do with Vantage. It will be
used to capture parameters from process stations on the production
floor.



Mark



________________________________

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of Dale R. Kalsow
Sent: Monday, October 08, 2007 3:56 PM
To: vantage@yahoogroups.com
Subject: RE: [Vantage] OT: MS Access



Mark,

If you start dumping in data using access you could corrupt or not
maintain the data integrity in Vantage. Only through using the vantage
application can this be maintained 100%.

If you want to use access for reporting, no updates, you might be
alright but this is why crystal reports is there. I hope this helps.

Dale Kalsow | Information Technologies Director
__________________________________________________________
Determan Brownie, Inc. | 1241 72nd Avenue NE | Minneapolis, MN 55432

* Phone: (763) 502-9689 | * Fax: (763) 571-1789

* dale.r.kalsow@... <mailto:dale.r.kalsow%40determan.com> | *
http://determan.com/ <http://determan.com/>

"Ambition is the path to success. Persistence is the vehicle you arrive
in."

Electronic Privacy Notice. This e-mail, and any attachments, contains
information that is, or may be, covered by the Electronic Communications
Privacy Act, 18 U.S.C. 2510-2521, and is also confidential and
proprietary in nature. If you are not the intended recipient, please be
advised that you are legally prohibited from retaining, using, copying,
distributing, or otherwise disclosing this information in any manner.
Instead, please reply to the sender that you have received this
communication in error, and then immediately delete it. Thank you in
advance for your cooperation.

________________________________

From: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
[mailto:vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> ] On
Behalf
Of dupuismd
Sent: Monday, October 08, 2007 2:55 PM
To: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
Subject: [Vantage] OT: MS Access

Hello group
I have an off topic kind of question. What are the pro's/Cons of
building a MS Access database and putting it on a server for use by a
dozen clients? I have in the past heard of problems with record
locking and data corruption. I have seen an Access data base lock up
requiring frequent rebuilds. This again is old history, has anything
changed with this product?

TIA
Mark

[Non-text portions of this message have been removed]





[Non-text portions of this message have been removed]
5
I only use Access for my reporting and have not had any problems. I
think the key is to ensure you have the ODBC setup for read-only and
hide the tables and queries from the user by building switchboards for
them. I also run the databases local on the user's pc with a few custom
tables on the server which I link to. I have not had any problems of
lockups or data corruption.



Butch



________________________________

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of dupuismd
Sent: Monday, October 08, 2007 12:55 PM
To: vantage@yahoogroups.com
Subject: [Vantage] OT: MS Access



Hello group
I have an off topic kind of question. What are the pro's/Cons of
building a MS Access database and putting it on a server for use by a
dozen clients? I have in the past heard of problems with record
locking and data corruption. I have seen an Access data base lock up
requiring frequent rebuilds. This again is old history, has anything
changed with this product?

TIA
Mark





[Non-text portions of this message have been removed]
6
As long as it is stand alone you should be fine from a vantage
standpoint. As far as the reliability of MS Access; it is greatly
improved. Watch how you write the queries and what fields you are
accessing and you should be just fine. Do routine maintenance on the db
and you will be good to go.



Feel free to give me a call if you have any questions. I have do a lot
of development in access in the past.



Dale Kalsow | Information Technologies Director
____________________________________________________________________
Determan Brownie, Inc. | 1241 72nd Avenue NE | Minneapolis, MN 55432

* Phone: (763) 502-9689 | * Fax: (763) 571-1789

* dale.r.kalsow@... | * http://determan.com/



"Ambition is the path to success. Persistence is the vehicle you arrive
in."



Electronic Privacy Notice. This e-mail, and any attachments, contains
information that is, or may be, covered by the Electronic Communications
Privacy Act, 18 U.S.C. 2510-2521, and is also confidential and
proprietary in nature. If you are not the intended recipient, please be
advised that you are legally prohibited from retaining, using, copying,
distributing, or otherwise disclosing this information in any manner.
Instead, please reply to the sender that you have received this
communication in error, and then immediately delete it. Thank you in
advance for your cooperation.

________________________________

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of Dupuis, Mark
Sent: Monday, October 08, 2007 3:06 PM
To: vantage@yahoogroups.com
Subject: RE: [Vantage] OT: MS Access





Actually this database will have nothing to do with Vantage. It will be
used to capture parameters from process stations on the production
floor.

Mark

________________________________

From: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
[mailto:vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> ] On
Behalf
Of Dale R. Kalsow
Sent: Monday, October 08, 2007 3:56 PM
To: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
Subject: RE: [Vantage] OT: MS Access

Mark,

If you start dumping in data using access you could corrupt or not
maintain the data integrity in Vantage. Only through using the vantage
application can this be maintained 100%.

If you want to use access for reporting, no updates, you might be
alright but this is why crystal reports is there. I hope this helps.

Dale Kalsow | Information Technologies Director
__________________________________________________________
Determan Brownie, Inc. | 1241 72nd Avenue NE | Minneapolis, MN 55432

* Phone: (763) 502-9689 | * Fax: (763) 571-1789

* dale.r.kalsow@... <mailto:dale.r.kalsow%40determan.com>
<mailto:dale.r.kalsow%40determan.com> | *
http://determan.com/ <http://determan.com/> <http://determan.com/
<http://determan.com/> >

"Ambition is the path to success. Persistence is the vehicle you arrive
in."

Electronic Privacy Notice. This e-mail, and any attachments, contains
information that is, or may be, covered by the Electronic Communications
Privacy Act, 18 U.S.C. 2510-2521, and is also confidential and
proprietary in nature. If you are not the intended recipient, please be
advised that you are legally prohibited from retaining, using, copying,
distributing, or otherwise disclosing this information in any manner.
Instead, please reply to the sender that you have received this
communication in error, and then immediately delete it. Thank you in
advance for your cooperation.

________________________________

From: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
<mailto:vantage%40yahoogroups.com>
[mailto:vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
<mailto:vantage%40yahoogroups.com> ] On
Behalf
Of dupuismd
Sent: Monday, October 08, 2007 2:55 PM
To: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
<mailto:vantage%40yahoogroups.com>
Subject: [Vantage] OT: MS Access

Hello group
I have an off topic kind of question. What are the pro's/Cons of
building a MS Access database and putting it on a server for use by a
dozen clients? I have in the past heard of problems with record
locking and data corruption. I have seen an Access data base lock up
requiring frequent rebuilds. This again is old history, has anything
changed with this product?

TIA
Mark

[Non-text portions of this message have been removed]

[Non-text portions of this message have been removed]





[Non-text portions of this message have been removed]
7
We use MS-Access for several shared databases. The largest is currently 200MB, shared by 9 people and is definitely "mission critical" (our quoting system). Never had much problem with it AND...it is still Access-95. Only issue lately is it won't run on PCs with over 1GB RAM. I did not write it and it has some quirky macros that will not convert to Access-2000 and beyond so we live with it....until Vantage 8.x anyway when PCs must have 2GB of RAM. I will replace the Access system with Vantage 8.x screen mods, etc... At one point it had grown to 600MB but I purged old records and compressed it so it now runs much faster.
-Todd C.

________________________________
From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of dupuismd
Sent: Monday, October 08, 2007 2:55 PM
To: vantage@yahoogroups.com
Subject: [Vantage] OT: MS Access


Hello group
I have an off topic kind of question. What are the pro's/Cons of
building a MS Access database and putting it on a server for use by a
dozen clients? I have in the past heard of problems with record
locking and data corruption. I have seen an Access data base lock up
requiring frequent rebuilds. This again is old history, has anything
changed with this product?

TIA
Mark



________________________________
The information contained in this E-mail message and any documents which may be attached are privileged and confidential, and may be protected from disclosure.

Please be aware that any use, printing, copying, disclosure or dissemination of this communication may be subject to legal restriction or sanction. If you think you have received this message in error, please reply to the sender.

For more information please visit www.harveyvogel.com


[Non-text portions of this message have been removed]
8
Mark,

I believe what you are saying is creating an MS Database that has
nothing to do with Vantage. I have done those, some that extract
information from 6.1 for informational purposes (customer information,
pending quotes, etc. for an Access Salesperson Workbench) and even
updated information in Vantage (mostly text fields) after trying
extensively in test databases.

Stand alone databases are OK for multiple users (even Terminal Server
users). I would not have multiple users using a database that modifies
comments or lock prices in orders lines (something I have done before)
or extract information from Vantage constantly. Every user that hits the
ODBC connection is a license used (keep that in mind) and has the
possibility to slow down every regular user. If you need to update from
Vantage, I would assign 1 user to update tables linked to Vantage and
multiple users could get access to updated tables after the update is
done.

Good luck!

Mario E. Aguirre - IT Manager
Lakin General Corporation, Inc.

________________________________

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of dupuismd
Sent: Monday, October 08, 2007 2:55 PM
To: vantage@yahoogroups.com
Subject: [Vantage] OT: MS Access



Hello group
I have an off topic kind of question. What are the pro's/Cons of
building a MS Access database and putting it on a server for use by a
dozen clients? I have in the past heard of problems with record
locking and data corruption. I have seen an Access data base lock up
requiring frequent rebuilds. This again is old history, has anything
changed with this product?

TIA
Mark






[Non-text portions of this message have been removed]
9
Thanks for the feedback everyone



Sounds like my fears may be unfounded with the latest MS Access
offering.



Mark



________________________________

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of Todd Caughey
Sent: Monday, October 08, 2007 4:18 PM
To: vantage@yahoogroups.com
Subject: RE: [Vantage] OT: MS Access



We use MS-Access for several shared databases. The largest is currently
200MB, shared by 9 people and is definitely "mission critical" (our
quoting system). Never had much problem with it AND...it is still
Access-95. Only issue lately is it won't run on PCs with over 1GB RAM. I
did not write it and it has some quirky macros that will not convert to
Access-2000 and beyond so we live with it....until Vantage 8.x anyway
when PCs must have 2GB of RAM. I will replace the Access system with
Vantage 8.x screen mods, etc... At one point it had grown to 600MB but I
purged old records and compressed it so it now runs much faster.
-Todd C.

________________________________
From: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
[mailto:vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> ] On
Behalf Of dupuismd
Sent: Monday, October 08, 2007 2:55 PM
To: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
Subject: [Vantage] OT: MS Access

Hello group
I have an off topic kind of question. What are the pro's/Cons of
building a MS Access database and putting it on a server for use by a
dozen clients? I have in the past heard of problems with record
locking and data corruption. I have seen an Access data base lock up
requiring frequent rebuilds. This again is old history, has anything
changed with this product?

TIA
Mark

________________________________
The information contained in this E-mail message and any documents which
may be attached are privileged and confidential, and may be protected
from disclosure.

Please be aware that any use, printing, copying, disclosure or
dissemination of this communication may be subject to legal restriction
or sanction. If you think you have received this message in error,
please reply to the sender.

For more information please visit www.harveyvogel.com

[Non-text portions of this message have been removed]





[Non-text portions of this message have been removed]
10
I've developed over 200 Access applications. The answer to your
questions is: it depends. Access is a very stable database development
and application program. It can run applications with 100's of users.
It depends #1: Application speed and record locking will depend upon the
speed of the hardware. I would suggest that you put the data (back end)
on a server drive that has miminal contention or none at all if
possible. You will want to keep that drive clean so that fragmentation
won't be a problem. If you have a lot of files and activity on that
drive it could create problems. Be sure that the database is in the root
directory rather than down one level or several levels of directories.

It depends #2: Put the front end application on the clients C drive. I
use C:\Apps.

It depends #3: Compact and repair the back end data weekly and maybe
even daily if it has a lot of updating activity. You can use a product
from FMS that will automate this.

It depends #4: Don't use macros, use VBA so that you can trap errors.
Write these errors to an error logging table. It will help resolve
user/application problems. It will also show you if you have record
locking problems. I started doing this about 7 years ago and found it to
be one of the most important things I ever did. It takes extra time but
is well worth it. I don't do this on all applications. Only if the
database is has a lot of activity and is critical.

It depends #5: How many tables will the database have and how many
records in each table? The size of the database will affect application
performance.

It depends #6: Do you know how to design the table with proper keys and
indexes? A poorly designed database will have more problems.

It depends #7: This is the big issue!! Will all of the users be doing
constant updating? Will they ever access the same record and try to
update it? How the users use the application will be a big factor in
the speed of the application and if you will have any record locking
issues.



There are many more factors that will affect performance and record
locking. At some point, if necessary, you could upsize the back end to
SQL which will handle all of the record locking for you.



I'm not sure what you mean by a database locking up and requiring
frequent rebuilds. If you are referring to compact and repair that
should be done at least weekly anyway. Over the last 14 years of using
Access I have had 3 cases where the database got corrupted and where the
compact and repair did not fix it. I think that is a pretty good
record. However, you do have to be aware that it can happen. Then you
will have to open the tables, find the corrupted record and delete it or
rebuild the table by copying the records. Be sure and keep it backed
up.



Access 2000 was a major improvement over the previous versions. I don't
worry about any application in that version or later. Early versions I
convert to at least Access 2000.



If you have any further questions you can give me a call.



Lon A. Wiksell

ROM Corp.

913-219-6565



________________________________

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of dupuismd
Sent: Monday, October 08, 2007 2:55 PM
To: vantage@yahoogroups.com
Subject: [Vantage] OT: MS Access



Hello group
I have an off topic kind of question. What are the pro's/Cons of
building a MS Access database and putting it on a server for use by a
dozen clients? I have in the past heard of problems with record
locking and data corruption. I have seen an Access data base lock up
requiring frequent rebuilds. This again is old history, has anything
changed with this product?

TIA
Mark





[Non-text portions of this message have been removed]