Thank you for the response.
The only change that I made to the db was to add one
calculated field to an existing report. There were no
changes that would require a library reference change.
Also, my program is not distributed as a packaged
installation. We are a small company and all workstations
have Office 2000. Therefore, I just copy the frontend mdb
to each workstation. Since the db has security setup, the
workstation applications are run using the shortcut I
mentioned before with the /runtime parameter.
Also, as I previously mentioned, the problem does not
exist if I save my changes, compact, and copy the mdb to
the workstations. The problem only occurs if I save my
changes, compact, decompile, compile, compact, and copy
the mdb to the workstations.
Thanks again for the suggestions.
Jean
>-----Original Message-----
>Hi Jean,
[quoted text clipped - 46 lines]
>| The shortcut command line is:
>| "C:\Program Files\Microsoft
Office\Office\MSACCESS.EXE" "C:\TKData\TKDB.mdb" /wrkgrp "\
>| \TKServer-Bkup\$TKData\Custsrvc.mdw" /runtime
>|
[quoted text clipped - 70 lines]
>
>.
Alick [MSFT] - 29 Sep 2003 04:28 GMT
Dear Jean,
I did some tests and it works fine.
"D:\Program Files\Microsoft Office\Office\MSACCESS.EXE" "d:\test.mdb"
/wrkgrp "\\sha-com-01\public\aaa\system.mdw" /runtime
I would suggest you create a new database and importing all the objects
into the new one, and then deliver the database to the clients. Before
delivering the database to the client, please make sure it works on your
side.
Sincerely,
Alick Ye, MCSD
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
--------------------
| Content-Class: urn:content-classes:message
| From: "Jean" <Jean@NoSpam.com>
[quoted text clipped - 179 lines]
| >
| >.