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!!
