Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion GroupsFormsForms ProgrammingQueriesModules / DAO / VBAReports / PrintingMacrosDatabase DesignSecurityConversionImporting / LinkingSQL Server / ADPMultiuser / NetworkingReplicationSetup / ConfigurationDeveloper ToolkitsActiveX ControlsNew UsersGeneral 1General 2
Access DirectoryToolsTutorialsUser Groups
Related Topics
SQL ServerOther DB ProductsMS OfficeMore Topics ...

MS Access Forum / New Users / August 2006

Tip: Looking for answers? Try searching our database.

access runtime locks

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Carol - 01 Aug 2006 17:08 GMT
I have developed an access runtime application in 2003 Developer (XP) that is
looking at a database on a server and being used by multible users as an
inquiry only. I am getting "Locks" on the server and when this happens nobody
can get in. Most of the users are on Office 2000. I am using Office XP. Seems
like the locks come when I get in the database.

Also a another problem a few users have the full version of access and the
runtime and when they go in to explorer and open up an access database it
defaults to the runtime version instead of the full access.  When I do it, it
defaults to the full version. We have tried to use the "Open with..." and
default to the full version, but does not work.

Is all of these problems a conflict of 2000 vs 2003.
Albert D. Kallal - 03 Aug 2006 06:26 GMT
> Is all of these problems a conflict of 2000 vs 2003.

Well, as a general rule, if you do run a mixed environment, then you should
either create the mde in a2000, and distribute that to each pc, or perhaps
(more work), distribute a mde to each machine based on the SAME version of
ms-access.

Your back end data (the part on the server) will obviously have to remain in
a2000 format so both a2000, and a2003 can use the application.

So, splitting likely would fix a lot of problems for you. As for "getting
locks" on the server, it is not quite clear what you mean.

Anyway, to learn about splitting, you can read the following..as it explains
not only that you should split, but WHY you split...

http://www.members.shaw.ca/AlbertKallal/Articles/split/index.htm

Signature

Albert D. Kallal
Edmonton, Alberta Canada
pleaseNOOSpamKallal@msn.com

 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.