Your application should be split into a front-end (containing the queries,
forms, reports, macros and modules), linked to a back-end (containing just
the tables). Only the back-end should be on the server: each user should
have his/her own copy of the front-end, preferably on their hard drive. (In
actual fact, this is how it should have been set up in Access 97 as well)
--
Doug Steele, Microsoft Access MVP
http://I.Am/DougSteele
(no e-mails, please!)
"yuggol" <yuggol[ at ]discussions.microsoft.com> wrote in message
news:060A89CD-06EB-495B-89F3-58A66661F568[ at ]microsoft.com...
[Quoted Text] >I have a multiuser database that runs some code to print a report to a pdf
> file using Acrobat Distiller. Distiller is configured to NOT prompt for
> file
> name & always overwrite any existing file. This DB has just been converted
> from 97 to 2003. This process worked great in 97, I would rename the
> report
> to a field from a recordset, then open the report using the same field as
> the
> filter & I would end up with a 1 page pdf file for the specified filter
> with
> the file name also being the filter.
>
> Example recordset:
> 1000
> 1001
> 1002....
>
> Folder after printing:
> 1000.pdf
> 1001.pdf
> 1002.pdf....
>
> Now that the DB has been converted to 2003 I can no longer run this
> process
> because M/S will not allow me to rename the report unless I have exclusive
> access to the DB.
>
> Does anyone have a workaround for this situation?
>
|