Dual use of Access database problem

[HLotis]

Has anyone used an Access database on a web server while it was also being used concurrently by an Access application?<br><br>What are the requirements and locations for the web server and for the dual use database?<br><br>I currently have a small LAN/WAN application for a small user community of 10 Help Desk technicians. While most of the work probably will be done via MS Access97, dual updates by an Intranet Browser needing access is also a possibility. Developer vs. User Rights and amenability to accept changes seem to be an issue.<br><br>1. What are the requirements for the server and for the location of the database? <br>2. Great need for LAN security<br>3. Security, Developer vs. User Rights and amenability to make and accept changes seem to be the issue. Are there any other hidden problems?<br><br><br><br>

 

[palbano]

Dear HLotis,<br><br>Sound like your trying to use a hammer to build a Indy Racer. In my experience you will put in many hours of work trying to find the answers to these questions and in the end one of two things is likely to happen 1) The solution will not hold up to the use probably due to using Access as the datasource. 2) One of the requirements just can not be met when using Access.<br><br>I would seriously consider moving to SQL Server.<br><br>&quot;But, that's just my opinion... I could be wrong&quot;.<br>-pete

 

[HLotis]

Use of SQL server requires an NT server and licenses and training all which cost more than we have. We have 15 users and no more than 3-5 concurrent users and we are familiar with Access97 which is on every desktop. We only intend to use browsers for very simple functioning like updating one field or searching for a small list. The life expectancy is one year. The project is due in two weeks.

 

[bookouri]

i also have a small access database, Up until recently Ive used it to provide asp pages through our web page. I had a copy for the clerks to update and every few days Id copy the updated mdb file to the web page. Because the application has grown I decided to make a share on the web server and let the clerks update the data directly. Now, if anyone has the database open my web server asp pages come back with a database in use error. None of the asp pages do anything but retrieve a list of names, no modifications, edits etc are done on the web server. Other than that, access has been fully adequate for our small applications.
Other security issues are not really different from basic stuff. Set the NTFS permissions and share permissions appropriately.