Runs on one machine and not another: Error 3075

  • Thread starter Thread starter Sam Goforth
  • Start date Start date
S

Sam Goforth

I open a report in a module and return there. Everything works great on one
machine but error 3075 occurs each time as the report is closed on a second
machine under Assess runtime. The error is reported from the module which
calls the report. I have tried dozens of ways to locate the source of the
error with no luck. HELP!
 
When the report is closed is there any code?
what is the next thing that happens?
Has your code been compiled
does the Runtime version include all the relevant controls and dll's

I had similar problems with Access runtime where my app ran perfectly well
on the development computer but various errors came to light when using
runtime
 
Newbie said:
When the report is closed is there any code?
Click to expand...

The calling module has this code where strObject = "List" and the 1 is used
to control line spacing in the report:
Sub MasterOutput(strObject)
(DIM etc.)
Select Case strObject
Case "List"
DoCmd.OpenReport "rptRetirees", acViewPreview, , , , 1
Case "Labels"
PrintLabels
Case "Mail Merge"
OutputMailMergeFile
Case "Contacts"
ExportContacts
Case Else
End Select
Exit_MasterOutput:
' frmSelectPersons is used to specify parameters for query and filter
If IsLoaded("frmSelectPersons") Then DoCmd.Close acForm,
"frmSelectPersons"
Exit Sub
(Error handler - THIS ERROR HANDLER DISPLAYS THE ERROR MESSAGE)
EndSub

The close event for the report has the following code:
Private Sub Report_Close()
Call ToolBarShow("MainToolbar", True)
Call ToolBarShow("PrintRetirees", False)
DoCmd.Restore
End Sub
what is the next thing that happens?
Click to expand...
As soon as the report displays in preview mode, control returns to the
"MasterOutput" sub and subsequently to a switchboard (the MS supplied
version).
Has your code been compiled yes
does the Runtime version include all the relevant controls and dll's
Click to expand...
As best as I can determine, yes. The packaging wizard was used. (All this
takes place under Windows XP Home and Office XP Developers edition.)
 
That's not very helpful . . .

If everything works ok on the dev machine then it must be something to do
with the install of access runtime.
Check all the references that are used and any activex controls - make a
note of the files and repackage the app. Make sure all the files are
included.
I found that I had to manually add files to the package as the Wizard didn't
pickup all the correct files
 
I agree that the error description is not helpful! That is one reason that I
have been going around in circles for a couple of weeks.

I am not confident that all needed references and no extraneous ones are
included. Can you suggest a readily available reference on how to check
references? Neither the Access 2002 help file nor the Developers help file
are very useful.

Incidentally, the db had been running OK on the distributed machine until
recently. However I can't pin down the point at which the problem started.
It could have been a change in my code or one of the updates in Office.

Thanks for all your input.
 
Back
Top