Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion GroupsFormsForms ProgrammingQueriesModules / DAO / VBAReports / PrintingMacrosDatabase DesignSecurityConversionImporting / LinkingSQL Server / ADPMultiuser / NetworkingReplicationSetup / ConfigurationDeveloper ToolkitsActiveX ControlsNew UsersGeneral 1General 2
Access DirectoryToolsTutorialsUser Groups
Related Topics
SQL ServerOther DB ProductsMS OfficeMore Topics ...

MS Access Forum / Multiuser / Networking / September 2003

Tip: Looking for answers? Try searching our database.

Decompile causes runtime error

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Jean - 23 Sep 2003 17:29 GMT
I have a multiuser Access 2000 db on a Win2K network that
has recently developed a problem.

The history...I have a backend Access 2000 db on a Win2K
Server. Each workstation (they all run Win2K Prof.) has
the frontend Access 2000 db. The workstation programs are
run from a shortcut using the /runtime parameter.

In the past, everytime I made changes to the frontend, I
would decompile and compact it before copying it to the
workstations. This worked great.

Recently our LAN Admin upgraded all of the workstations to
Win2K SP3 and Office 2000 SP3. I had previously upgraded
my development machine to Win2K SP4.

Yesterday I made a change to the db. This is the first
change since any of the upgrades were performed. When the
users tried to access the db this morning, they all got
past the login screen and the splash screen, but when the
program attempted to access the tables on the backend,
they got a runtime error and the app closed.

I have narrowed the problem down to the decompile process.
If I compact without decompiling, the users can access the
program with no problem.

Any ideas how to fix this situation (other than not doing
a decompile)? The decompile has really helped in the past
with performance.

Any help is greatly appreciated.

Thanks,
Jean
Alick [MSFT] - 24 Sep 2003 05:07 GMT
Hi Jean,

Do all the users have such issue? What is the full/exact run time error
message? Could you post the full command line you used in the shortcut?

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 - 34 lines]
| Thanks,
| Jean
Jean - 24 Sep 2003 13:44 GMT
Yes all users have the same problem.

The exact error message is:
Execution of this application has stopped due to a run-
time error. The application can't continue and will be
shut down.

The shortcut command line is:
"C:\Program Files\Microsoft
Office\Office\MSACCESS.EXE" "C:\TKData\TKDB.mdb" /wrkgrp "\
\TKServer-Bkup\$TKData\Custsrvc.mdw" /runtime

>-----Original Message-----
>Hi Jean,
[quoted text clipped - 51 lines]
>
>.
Alick [MSFT] - 25 Sep 2003 03:47 GMT
Hi Jean,

How about Robert's suggestion? In addition, you mentioned you made some
modification in the database; it is possible you have run into some known
issue:

ACC2000: Filter-by-Form Example for Run-Time Apps Available,
http://support.microsoft.com/support/kb/articles/q262/0/99.asp

The error may be caused by not including a reference in your database to
a library your application needs. For instance, if you have code that
automates Excel, you will need to make a reference to the Microsoft Excel
9.0
Object Library in your database; this library file will then be included in
the runtime package when you go through the Package and Deployment Wizard.
Especially, if you use ADO in your code, it is possible the application is
referencing a newer version of ActiveX Data Objects (ADO) than the one that
is installed on the deployment computer. One method is to change the ADO
reference in your application to match the version  on the deployment
computer.

If your modified code contains END statement, I suggest you rewrite the
code so it does not use the "End" statement. If it is appropriate, you can
use the "Exit Function" statement to exit the procedure.

Please feel free to reply to the threads if you have any concern or
questions.

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 - 81 lines]
| >
| >.
Jean - 25 Sep 2003 14:09 GMT
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]
| >
| >.
david epsom dot com dot au - 25 Sep 2003 23:28 GMT
Please, what is the error if it is run without the
/runtime command line option?

However, when your database is so trashed that a
/decompile makes it worse, it is time to restore
to backup or attempt importing to a new database.

(david)

> Yes all users have the same problem.
>
[quoted text clipped - 78 lines]
> >
> >.
Jean - 26 Sep 2003 13:29 GMT
The users get the same error with or without the /runtime
command line option.

>-----Original Message-----
>Please, what is the error if it is run without the
[quoted text clipped - 15 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]
>
>.
david epsom dot com dot au - 28 Sep 2003 22:31 GMT
The message quoted looks like it is specific to the
runtime environment ("The application can't continue
and will be shut down"). Do these PC's have full
retail Access installed?

Assuming that these PC's do have full retail Access,
the message seems to indicate a corrupt 'project'
-- which I guess we knew already.

(david)

> The users get the same error with or without the /runtime
> command line option.
[quoted text clipped - 104 lines]
> >
> >.
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.