[AccessD] App using Runtime?

Anythoughts on Compacting without loading access?

Thanks,

Mark


> Date: Fri, 1 Feb 2008 10:25:41 -0500
> From: jimdettman at verizon.net
> To: accessd at databaseadvisors.com
> Subject: Re: [AccessD] App using Runtime?
>
> Mark,
>
> < it?>>
>
> Creation and the maintaining of the .LDB file is a function of JET, not
> Access. Access does not need to be installed (full or runtime) to use a JET
> backend with an app (say written in VB or C++).
>
> Jim.
>
> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com
> [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Mark A Matte
> Sent: Friday, February 01, 2008 10:07 AM
> To: Access Developers discussion and problem solving
> Subject: [AccessD] App using Runtime?
>
>
> Hello All,
>
> An old app showed up...it is not access...but uses an mdb(A97) as a back
> end. When the app is running...there is and LDB present? Access is NOT on
> the machine.
>
> Does this mean that the runtime is being used?...if so, how do I find it?
>
> The problem is the company is migrating to XP...and the users used to use
> A97 to go in and compact this mdb...and converting the mdb to XP seems to be
> a problem. If the runtime were on the machine...I could drop an A97 mde on
> that machine that compacts the mdb...
>
> Thanks,
>
> Mark A. Matte
> _________________________________________________________________
> Need to know the score, the latest news, or you need your HotmailR-get your
> "fix".
> http://www.msnmobilefix.com/Default.aspx
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com

_________________________________________________________________
Need to know the score, the latest news, or you need your Hotmail®-get your "fix".
http://www.msnmobilefix.com/Default.aspx