Access slow saving a report to mdb on a netware server

[mcvickerp]

I have a front-end access file that is located on a novell server.

Since I have upgraded to Windows XP Professional SP2 and Access 2003, the
time to save a report to the file has gone up dramatically. The application
creates custom reports and saves them to a PDF for each client. I use to be
able to create 7 PDFs a minute. Now I can do only 1 PDF for every two
minutes when using the server. I have isolate this down to the server
because when I run the file from the local computer, I return to the 7 PDFs
per minute.

The data exists on the server. I have no problem looking at querys or
previewing reports. The slowness only shows when Access is saving a change
back to the report.

Windows XP Professional 5.1.2600 Service Pack 2 Build 2600
Office Access 2003 (11.6355.6360) SP1
Novell is the latest version
The access file is digitally signed (locally)

Anyone have any ideas on how to restore the speed back?

Paul McVicker
pmcvicker at mail.mhanet.com

 

[Albert D. Kallal]

I have a front-end access file that is located on a novell server.

I can assume you thus have a "split" database?

I will save the issue that you need to put this FE on each
workstation...especially if this is a multi-user application. If it is
not..then you can safely leave the FE on the server with the BE.

The data exists on the server. I have no problem looking at queries or
previewing reports. The slowness only shows when Access is saving a
change
back to the report.

Try keeping a persistent connection. Do this during development to change
the report..and also while running the code. A persistent connection simply
means to keep a connection open to the back end database from the Front end.
You can simply open up any old table while in the front end (this table you
open is obviously a linked table to the back end). Now, just minimize the
table. If you run your code, or develop..you will find performance returns
to the same as if you put the database on your local computer...

Also, in addtion to you placing the FE on each workstation that runs the
applicaton, it should also be a mde....