03-10-2010 10:23 AM
Ok after creating a new build from scratch I'm looking much better...though I'm getting this error when looking to print from the exe. after installed (not getting this error from the actual un-deployed VI running on 9).... do I just need to change the file location to be one shallower or deeper so the "append control image.vi" can find it?
I've attached the error.
thanks for the help.
03-10-2010 10:37 AM
Also here's another error that comes up and locks up my exe.
It's all based on the llb and object classes...just need to know how to fix these, as I never have even touched this kind of programming.
03-10-2010 11:13 AM
jonathanupr,
I have some guesses at what could be going on with those error codes but before I went into that I wanted to point out this link (http://zone.ni.com/reference/en-XX/help/371361F-01/lvhowto/debug_apps_dlls/). This goes over how to create a debuggable executable. This is my personal first line of defense when I am building an executable that I works fine on my machine but not when I deploy it. Are you running your built executable on your machine or a "clean" machine?
The -2147352567 issue could be a naming issue (filepath) or simply the image you are trying to use doesn't exist. To check the filepath, you can use the debuggable executable to probe the block diagram and make sure that you are pointing to the right location. Sometimes even if you are pointing to the right location, file name, and capitalization and everything is right just adding the proper file extension will help the issue (i.e. .png). I would try those things out to make sure that your executable is behaving as you think it should be.
The -2147467259 issue is a little bit more hairy. This will depend on the question I asked earlier on whether you are trying your built executable on your development machine or not. If the error is saying you can't open the database and you are on your development machine, then I would check to make sure that there aren't any conflicts going on (database is reserved by something else running at the moment or something like that). If it is on the deployment machine, then I would check to see what version of Microsoft Access it has (I assume you are using Access based on the error but if not then let me know) and that you have permission to open that database from the other computer. This one might take more steps to figure out what's really going on but again the debuggable executable can help step through and figure out what's going on.
We (the community) are here to help out so just let us know what's going on and I'm sure that we will be able to get this all straightened out.
Cheers!!
03-10-2010 11:25 AM
03-11-2010 10:25 AM
jonathanupr,
What's the verdict on the executable today? Did the debugging help out? Just let us know if you're still getting the errors or any new insights so we can consult the LabVIEW oracles for guidance
03-11-2010 02:09 PM
things didn't work out... I looked at debugging the code in a variety of ways, but didn't have any success nor saw any reason the code should've been acting the way it. (whenever I get a chance to get in touch with our Alliance Partner developer I'm just going to have to have him take a look at it).
I've tried going back to 8.5, though all of my toolkits are locked up in 9...
I've spent around 6 hours of deleting 9, and re-loading toolkits, and the 8.5 development system. Now the VIs in the Report Generation Toolkit 1.1.2 that was used in 8.5 are coming up broken... this is never-ending right now.
03-11-2010 02:48 PM
jonathanupr,
I hate to open the pandora box but what all did you check for just so we know where you stand? It might be a little late for troubleshooting now since you downgraded to 8.5.1 (if the Report Gen VIs are coming up broken...what errors or issues is it pointing to so we can get those solved?). If possible, start posting up some code that is causing issue so that the community can look through it and give some pointers.
03-15-2010 09:14 AM
jonathanupr,
Any luck with this issue? If not, post some of your code so we can start going through it and help figure out what's going on.