Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Chris Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Report Print Error using 2000 Runtime

Status
Not open for further replies.

southboy

Programmer
Oct 23, 2002
26
US
Our company installed all new computers which now uses the XP Operating System. All our in-house databases were created in Access 97 before the new computers, and now have to all be converted to Access 2003 using the Access 2000 format. Our Staff uses Access 2000 runtime to be able to access the databases.
I have an Access db created in Access 97. It had to be converted to Access 2000. The database converted fine to Access 2000 with out any errors and runs and performs as it should using MS Access 2003 software. (in Access 2000 format). The problem is I have a code in this data base that will print a selected record using a report when you click the “Print Selected” button. It works for myself because I’m using the actual MS Access 2003 (in Access 2000 format) software to run it, but our staff who only use the 2000 runtime, get the “Microsoft Access for Windows has encountered a problem and needs to close”. Error as soon as they click the “Print Selected” button and it closes out the Database.
I can’t click on the error debug button and look at the code because there using 2000 runtime and it won’t recreate itself when I run the database because I use the actual MS Access software and it works fine. Does anyone know why this code will not work using Access 2000 Runtime?

This is the code for the “Print Selected” button:

Private Sub Command107_Click()
'print selected keyword
On Error GoTo Err_Print_Click
varFilter = "Keyword='" & apostrophe(lstKeyword) & "'"
varFilterOn = True
DoCmd.OpenReport "rptNotes"
Exit_Print_Click:
Exit Sub

Err_Print_Click:
MsgBox Err.Description
Resume Exit_Print_Click
End Sub

Thanks In advance
 
The data are in 2000 format but the code is 2003, so I guess you have to use a 2003 runtime.

Hope This Helps, PH.
Want to get great answers to your Tek-Tips questions? Have a look at FAQ219-2884 or FAQ181-2886
 
Thank you for your prompt answer PHV. Tho your response is plausible, it is not something that can be done at the moment. Maybe I need to adjust my coding to something the 2000 runtime likes. Does someone have a better coding to send a selected record to a report?
 
Don't you have somewhere a full 2000 access version you may use to build the runtime version ?

Hope This Helps, PH.
Want to get great answers to your Tek-Tips questions? Have a look at FAQ219-2884 or FAQ181-2886
 
Is varFilter being dimensioned as a string somwhere else?
and
What is varFilterOn refering to?
 
Thanks for responding again. Hopefully we can figure out something together on this.

PHV – The runtime was just bought and pushed to all our machines by our PClan personnel when we went to XP late last year. With company money being what it is, I doubt I can get them to purchase a 2003 Runtime licensing for all our machines any time soon.

JKL0 The varFilter is set in the Modules section in a GlobalVariables module as

Global varFilter As String, varFilterOn As Boolean

This works fine inside MS Access but not the 2000Runtime.

I also have a button to attach the selected file as a .RTF text document to an email to be emailed out, that works fine in the 2000Runtime, but sending it to a MS Access report for print out does not.

 
Not sure about the syntax between 2000 and 2003, but you might try:

Public varFilter As String, varFilterOn As Boolean

This is untested as I don't have 2003 or 2000 runtime to try this out.
 
I doubt I can get them to purchase a 2003 Runtime
That is why I recommended (2 Feb 07 12:26) to build the deployed version with a full access with same version as your deployed runtime.

Hope This Helps, PH.
Want to get great answers to your Tek-Tips questions? Have a look at FAQ219-2884 or FAQ181-2886
 
After talking with the other Access programmer, (he is also experiencing problems using the 2000 Runtime.)
We presented a united front and have talked with our PC support supervisor and he will see about getting our staff
the 2003 runtime.
You all have been a big help!!
Thanks again.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top