code crashes on one machine, but not another

[Jackie]

I execute the same code on two different machines. On one machine it works without error. (Both machines are running Windows 95 and Access 97). On the second machine I get the following message:

The Detail Window associated with this error states, "MSACCESS caused an invalid page default".

The corresponding code is below.

After I step through the code using the debug, the code cycles through, produces a separate report for each POC and does not crash.

Private Sub Report_Page()

'Identify a variable to hold the report file name
Dim strReportName As String
Dim strDir As String
Dim strPOCName As String
Dim strDateMonth As String
Dim strDateDay As String
Dim strDateYear As String
Dim strDate As String

'Get the path for which to store the report
'Remember that the default directory must be set in Access via Options Menu

strDir = CurDir & "\POC_Proj_Num\"


'Create date for file name

strDateMonth = Format(Date, "mmm&quot
strDateDay = Format(Date, "d&quot
strDateYear = Format(Date, "yyyy&quot
strDate = strDateMonth & strDateDay & strDateYear

'Get POC name

strPOCName = Me!txt_POC

'Establish the report file name
strReportName = strDir & strPOCName & strDate & "." & "rtf"

'Save the report to a file
DoCmd.OutputTo acReport, "POC_Project_Num", "RichTextFormat(*.rtf)", strReportName


'Close the report to contine processing the remaining POC's reports
DoCmd.Close acReport, "POC_Project_Num"

End Sub




The first time the code is executed the code crashes on the
DoCmd.Close acReport, "POC_Project_Num" line.

 

[Orion45]

I was getting a similar error in Access 2000 when a user did not have the same Microsoft service pack as everyone else. I'm not sure that this is the cause of your problem but it might be worth a try. You could also make sure that both PCs have the same resource libraries installed and enabled.

 

[mp9]

Maybe you could try working through

http://support.microsoft.com/default.aspx?scid=kb;en-us;148424

http://www22.brinkster.com/accessory/

 

[Jackie]

Thank you. I will start with verifying the resource library and procede from there.
What is puzzleing is that the code worked on both machines. I am not sure what changed on the machine in which the error is occuring.

 

[JohnLowell]

Take out the Docmd.close

You don't need it. The report isn't open when you use OutputTo.

 

[Jackie]

When I remove the DoCmd.close the report is not run for the remaining POCs.

The application is set up as a client/server configuration. The data (backend) is stored on a network server.

The report is executed by the followiong code:

Private Sub cmd_PM_Due_date_Click()
Dim dbMLV As Database

Dim rstFindProj As Recordset

Dim strFindPM As String


Set dbMLV = CurrentDb
Set rstFindProj = dbMLV.OpenRecordset("qry_find_program_mgr&quot

'Run if records in the file
If rstFindProj.RecordCount > 0 Then

Do While Not rstFindProj.EOF

'Identify the program manager for which to run the report
strFindPM = rstFindProj.Fields("PM&quot
'Run the report for the specific PM
'Report is also sent to a file
'DoCmd.OpenReport "POC_Due_Date", acPreview, "", "[qry_POC_Due_Date].[POC_Name] = """ & strFindPM & """"
DoCmd.OpenReport "PM_Due_Date", acPreview, "", "[qry_PM_Due_Date].[PM] = """ & strFindPM & """"
'Advance to the next Point of Contact for which to run the report
rstFindProj.MoveNext
Loop

'Tell the user the reports are finished
MsgBox "Point of Contact by Fabrication Completion Date Reports Completed."

End If
End

End Sub

 

[DerfLongshanks]

I have had a similar problem, which I found was caused by the page setup options. The original machine was setup for A3 and the second machine A4, once I had changed this it worked correctly.

Hope this helps