I'm writing an application for a client that is clinging tightly to the old days. They still run XP and Office 2003 on most of their machines. I'm developing in a Win 7/Office 2007 environment.
One of their programs is written to import data from Excel. There is no reference to Excel until / unless you run that program.
They have a test machine for me. It has Access Runtime installed, along with Office 2003. When they launch my program (front-end .accde linked to several .mdb files) they get a message "Searching for Excel." It appears for around 10 seconds and then disappears.
When they launch my program using the .accdb version of the same database, they get an error message. They can click through it and continue. Various odd errors pop up when we're testing (we don't test the import anymore, it works okay). Also, one error I've seen perplexes me
-Error 3075, line 0 function is unavailable in expression in query expression Format(Lastcall date,"mm/dd/yy")
Is that saying Format function is unavailable?
All this stuff works well for me in my testing on both runtime and full Access. Any ideas about why we see the various messages and errors?
Thanks,
Jim
One of their programs is written to import data from Excel. There is no reference to Excel until / unless you run that program.
They have a test machine for me. It has Access Runtime installed, along with Office 2003. When they launch my program (front-end .accde linked to several .mdb files) they get a message "Searching for Excel." It appears for around 10 seconds and then disappears.
When they launch my program using the .accdb version of the same database, they get an error message. They can click through it and continue. Various odd errors pop up when we're testing (we don't test the import anymore, it works okay). Also, one error I've seen perplexes me
-Error 3075, line 0 function is unavailable in expression in query expression Format(Lastcall date,"mm/dd/yy")
Is that saying Format function is unavailable?
All this stuff works well for me in my testing on both runtime and full Access. Any ideas about why we see the various messages and errors?
Thanks,
Jim
Comment