Re: Access 2002-2003 question (To mde or not? To install Access or not?)

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

You must. Access applications require either a full-blown Access or a runtime copy. Until the release of 2007, the only way to get a licensed copy of the runtime was to purchase the developers addition - named differently for each release of Office.



'====================================================
John Spencer
Access MVP 2002-2005, 2007
Center for Health Program Development and Management
University of Maryland Baltimore County
'====================================================


Tcs wrote:
I have a client on which I need to run Access. At a minimum I need to run a .mde. (This client is
only being used to allow an app on this client to gain access to data on our AS/400, via DB2 Connect
- PE (ODBC). This app will talk to the .mdX file on this client, which will look at only one linked
table on the AS/400. (This...(gulp)...*should* work.)

Access is not installed on this client. When I tried to run a .mdb, Windows wanted to install
Access. Hmmm... So I figured that what I needed was a .mde file. So I created one. After I moved
my .mde file to this client, when I tried to run this .mde, Windows wanted to...once again...install
MS Access. So...

Can anyone enlighten me as to just what the heck I need to make this work? This .mdb/.mde file only
needs to contain a link to just ONE TABLE (as far as I know). This link will be via ODBC (IBM DB2
Connect - Personal Edition) to our DB2 database on our AS/400.

-----

This is how I gain access to my data from my PC (my daily client). But unlike this new client PC,
my daily client PC *does* have MS Access installed. I don't *want* to install Access on this new
client PC...IF I DON'T HAVE TO. But will if I must.

Any help anyone can provide would be most appreciated. I thank you in advance...

Tom
.

Relevant Pages

  • Re: SQL Server 2005 Express OLEDB Connection from VB6
    ... Thanks for getting me to read this again and realizing they meant the client ... I think we'll stick with ODBC, since there is less to install on the client ... Microsoft SQL Server Native Client ...
    (microsoft.public.sqlserver.connect)
  • Re: DBD::DB2 where to get a client library
    ... I have managed to install ... not application development client) not a problem since we have them on the ... doesnot have rpm. ... you might want to check out the DB2 HOWTO ...
    (perl.dbi.users)
  • Re: Slow Application Access after joining the client to Domain
    ... When the same machine joins to the domain, the moment i click the application, it sends some RPC Packets to the DC and then i see some LSAT frames. ... After these frames only i see that the DB Client connecting to DB Server ... We are seeing a strange problem with one of DB2 Application. ...
    (microsoft.public.windows.server.active_directory)
  • Re: UDB2 software
    ... strictly something that runs on a PC client? ... websphere development studio I have a cd that says DB2 Unviersal ... I believe the big metal could run it under Linux as well but they also have their specialised z/OS version of DB2 much the same as the ISeries has its own version of DB2. ... I imagine it would have a centralised database component so you are going to be told to buy a UDB environment or that you can use the ISeries. ...
    (comp.sys.ibm.as400.misc)
  • Re: ODBC/Windows Client
    ... I tried the instaclient selection but that didn't install much, ... I would also need tnsping and the sql*net subsystem and whatever the ODBC driver needs but thats all. ... Instant Client is one way to go, but you need the basic Instant Client package and the ODBC Supplement. ...
    (comp.databases.oracle.server)