Re: VB6 App On MS Server

In article <7d22f72e-ed26-4541-a3cd-
829ab9ad8ccb@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>, nospama@xxxxxxxx says...
I have a VB6 application front ending a Access Database running in a
LAN with 6 concurrent users. All has been running very well with no
performance issues.
When we moved the application to a remote MS Server, we seem to be
experiencing some problems with less than stellar performance.
Here is how we have things installed:
The server hosts both the Access Database and 3 executables that make
up the entire project.
Each of the PC workstations have the OCX's, a dll, and all the
components required to access the database.
Generally speaking all of the workstation load "Program A" from the
server, which is an inquiry program into the database (No data
modification allowed).
The other 2 program are used occasionally to maintain the database.
When we attempted to run one of these maintenance programs, it
eventually seemed to hang, with the task manager on the workstation
saying "Program is not Responding".
Without getting into the gory details, the program reads all 12,000
records in the database, and is expected to create about 1800 new
records as a result of search. We have restarted the program several
times each time it would fail with the same result. In desperation we
copied the database and the executable involved to one of the
workstations, ran it without any problem whatsoever, then copied the
database back to the server. Fortunately this is done only once a
year, so I have a bit of a reprieve to find a solution to the problem.
BTW we had terminated all user of the applications so that we were the
only workstation accessing the database.

I have no experience in setting up an application in the environment
as I described so any suggestions with my application or how it is
implemented on the server would be greatly appreciated.

In addition to the other suggestions you have received, do some
searching on M$.com for "opportunistic locking".

--
Remove the ns_ from if replying by e-mail (but keep posts in the
newsgroups if possible).
.

Relevant Pages

  • Re: Problems networking Access
    ... linked to the backend on the server. ... When I enter records into the database from the workstation, ... A good approach is to build some type of search form, ...
    (comp.databases.ms-access)
  • Re: SQL Newbie question w SBS 2003 - confused - what to use
    ... Your database files can exist in different locations. ... SQL Server will allow a large number of concurrent users, ...
    (microsoft.public.sqlserver.programming)
  • Slow database
    ... Server is Win2K Server ... Workstation is XP Pro and or 2K Pro ... So today I thought I would rebuild a database ...
    (microsoft.public.access.externaldata)
  • Re: Too Many Client tasks
    ... You are either not closing database connections or there are just too many ... concurrent users for MS Access to accomodate. ... > error until I reboot the server. ...
    (microsoft.public.inetserver.asp.db)
  • Re: VB6 App On MS Server
    ... LAN with 6 concurrent users. ... The server hosts both the Access Database and 3 executables that make ... Generally speaking all of the workstation load "Program A" from the ...
    (microsoft.public.vb.general.discussion)