VB 5 & Crystal Reports

I am using Visual Basic 5.0 Professional Service Pack 3 and Crystal Reports 6. I have a problem when running reports @ runtime from the user PC's. It is an intermittent problem, when running the reports they receive an Automation Error - 2147417848 (80010108) - there is nothing special about the report - it just accesses an Access database stored on the main server. What could be causing this, I have looked on http://www.sagesoftware.com and their technical support but I have not yet found a solution to the problem. I am fairly new to programming VB with Crystal Reports - is there any way of trapping these errors so instead of the program "bombing out" it will only crash the report. The users are getting very frustrated with the application and it frustrates me further because I cannot fix the problem :-(

Please can anyone help me???

I look forward to hearing any advice.

Sorry to butt in on your question, you are writing what I'd like to learn about, where did you learn Crystal programming from?

can you recommend any books/sites?

Thanks!
Alex Read

I've just used the Visual Basic help for now

Hi Stevejo,

I had this problem too, it occurred after we migrated to WinNt. I never got a finger behind the cause but I've solved it by replacing the Crystal Reports control by the Crystal Reports Object Model. By doing so you avoid the OLE automation.

I don't know what version you are using and if it already supports the object model. I know 7.0 does so. Crystal reports as it comes with vb doesn't.

Succes.

i had a similiar problem...

check the references and make sure that
the reference to Crystal is lower on the list
than the DAO 3.51 Object Library reference.

also make sure that the OLE Automation is checked.

in References:
after OLE Automation should be
DAO 3.51
Crystal Report


hope it helps


larryn

Is the order in the referencelist significant ?
How come ?
Are there any rules of thumb I should know about regarding the references ?

the problem i had was that crystal
uses a DAO object and because of that
i was unable to reference MS DAO object
until i used DAO first in the references..

using crystal 8..