Question Please help! Access runtime errors

[tresky]

Hi, I have been creating database and programming in a couple different languages off and on for last 10 years or so. Never got too involved in it just minor programs, games, but I have made a ton a databases with ms access. I am I guess you could say not too fond of the new access, Im more old school and used to older versions. I have recently created a new database for the electrical contractor I work for that is VERY extensive. Tracking and updated all aspects of the commercial electric field, but specific to the foreman actually working in the field. It logs time, workers, all docs related to, reports, blah blah blah. The program is beautiful and I have been using it myself now for that last month or so just testing it out and tweaking minor things to speed up the proccess in the field. I have it almost ready, completely "stand alone" if you will, no need for ribbons or nav pane, all done is forms (pretty nice ones too I might add). Everything functions exactly as its supposed to, it is very complex though with a lot of update/append/delete queries, macros, code, custom functions...etc. When I package a solution or create an install file through the wizard, it even installs and opens like its supposed to (now in runtime, not access) but doesnt even recognize the basic "Date()" function, or "date()-weekday(date(),2)+7"...???...every button displays an error and crashes runtime, the only things that seem to work are the basic buttons which open a table, or basic form(mean no subforms recognized, no queries...) WHAT AM I NOT INCLUDING IN THE INSTALL PACKAGE??? OR WHAT AM I DOING WRONG. IF MY COMPANY HAD MS ACCESS INSTALLED ON THEIR SYSTEMS I WOULDNT HAVE THIS ISSUE, (I DONT THINK) ITS ONLY IN RUNTIME? PLEASE HELP? IM FRUSTRATED!

THANKS TO ANYONE!

 

[gemma-the-husky]

this is almost certainly due to a missing reference on the target machine.

not sure where it is in A2010 offhand, but check tools/references or the equivalent and one will be missing.

As an example

note that access resolves references upwards - so if you design for OUTLOOK2003 and EXCEL2003, and the target machine has OFFICE2007 - then the references will resolve correctly.

however if you design with OFFICE2007 (as is likely with A2007) - and the target machine only has OFFICE2003 then the references will fail, and need fixing.

They need to be fixed manually - but you cannot do this if you are supplying a mde/accde. (not even programmatically). In which case, you probably will need to use late-binding, rather than link the actual libraries.

hope this points you in the right direction.

 

[tresky]

Yes, it sounds like you are on to something here. Sorry but i understand what you are trying to say but how do i accomplish this? I am running a2007, and i have tried to install my program on two different win7 machines that do not have ms office at all, both failed. Also, i have installed it on my computer, which i designed it in, running a2007 also runtime, and it fails their as well. What im not understanding is if it doesnt even recognize basic functions on the machine which created it, what is a reason for that. Im assuming its because something similar to what you said, i am missing a reference to libraries/or something that wherever the program is looking to for the reference, it is not there. You would think the access wizard which compiles the files into an install package would include all the files/references nessesary for it to run in runtime... As you can probably tell, all the other databases ive made have been run in full access, this is my first time attempting to step outside that box, and it seems like pulling teeth! I love access and the ui and possibilities it provides, just wish microsoft would make things a little easier to understand for us who are not master programmers. If you wouldnt mind maybe a step by step for what you try here?

I am on a win7 machine running a2007, attempting to make my program run on any win machine with or with out ms office, or access...

 

[gemma-the-husky]

ok - in your own machine check the references, and please confirm which references you are using. then we can probably suggest which one is the culprit

a reference is actually a pointer to a dll (dynamic link library) or other source of common code modules available to any programme. on your machine, access can find the library. on the target machine, it cannot

if you check the references, you will be able to see the actual path to the dll (or other source) of the library.

one (or more) of these will not exist on your target machine.

if you are using runtimes you will not be able to fix this on the target machine. therefore you have to be sure the setup is correct.