C
Chris
Hi,
I've got a VB 5 application with a report setup form. The user chooses
the report and other choices using drop down boxes, check boxes etc.
There is a fair bit of code to fill the report tables in the database
and then the following code is executed.
objacces.DoCmd.OpenReport ReportName, acViewPreview
the problem is that in the report is VBA code that is using a textbox in the
detail
section of the report that is bound to a field in the report table.
This bound textbox should be picking up the value but I get a error 2427:
the object has no value.
If I put a break point in the VB5 app code and then resume after the break
point it works fine.
If I simply execute the report straight from access 97 and there is required
data in the report table(s) it works fine.
There is some kind of timing issue or something that is preventing the
access report VBA code from realizing there is perfectly good data and not
null for that textbox when firing from VB app.
I'm at a loss on this one. I understand it might be a glitch in Access 97
based on some google research and I have fixed a similiar problem using a
resume next error handling but this does'nt work this time.
thanks
Chris
I've got a VB 5 application with a report setup form. The user chooses
the report and other choices using drop down boxes, check boxes etc.
There is a fair bit of code to fill the report tables in the database
and then the following code is executed.
objacces.DoCmd.OpenReport ReportName, acViewPreview
the problem is that in the report is VBA code that is using a textbox in the
detail
section of the report that is bound to a field in the report table.
This bound textbox should be picking up the value but I get a error 2427:
the object has no value.
If I put a break point in the VB5 app code and then resume after the break
point it works fine.
If I simply execute the report straight from access 97 and there is required
data in the report table(s) it works fine.
There is some kind of timing issue or something that is preventing the
access report VBA code from realizing there is perfectly good data and not
null for that textbox when firing from VB app.
I'm at a loss on this one. I understand it might be a glitch in Access 97
based on some google research and I have fixed a similiar problem using a
resume next error handling but this does'nt work this time.
thanks
Chris