MSAccess Runtime issue

[tkanuradha]

Hi,



I'm using a access DB (v 2003) which has a front end driven by forms. The application takes an excel sheet to import data into the tables and does some processing to generate various reports. Application uses a form which calls a browse dialog for the user to choose his excel sheet to load data.

Problem is, the users at onsite cannot have msaccess installed in their locations as they are client machines.

Suggestion is to use the msaccess runtime. I'm having couple of questions here :

. I tried installing a runtime that was avlbl in a blog. I was able to open my mdb successfully but when i try to click on "browse" button to select the excel sheet for my application, i get a runtime error and application abruptly shuts down. I'm using Application.FileDialog code for the browse window to open.
. Is msaccess 2003 runtime avlbl free download? if so pls provide link
. Will my access db created in 2003 work with msaccess 2007 runtime?

Any help here is appreciated
Thanx in advance

[pbaldy]

The 2003 runtime was not available free; it was part of a developer toolkit. Your 2003 db will probably work fine with the 2007 runtime, but only testing will confirm that.

I'm curious that you say the users cannot have Access installed; the runtime is still Access, just a version of it without design capabilities.

[ajetrumpet]

tk,

you got 03 as a full version? the runtime shuts down when there's an error of course, as you're seeing. it should do the exact same thing if you test it in your full-version software.

the error probably has nothing to do with a compatibility issue. It's more than likely a syntax error, or other developer mistake.

[tkanuradha]

Adam,

The code works perfectly with full version software

tk,

you got 03 as a full version? the runtime shuts down when there's an error of course, as you're seeing. it should do the exact same thing if you test it in your full-version software.

the error probably has nothing to do with a compatibility issue. It's more than likely a syntax error, or other developer mistake.

[ajetrumpet]

Adam,

The code works perfectly with full version software

but what about Paul's post here? You try 07? which one threw errors? 07?

what computer threw the error? yours or theirs? is there an error message? what err handler do you have in there? can you change it to write the "err" object and some properties to a table? or to a text file maybe? anything to see if access prints out info for you with regard to the problem.

see where i'm going?