[AccessD] Access Workgroup Security [WAS: A97 and Win 7]

Charlotte Foust charlotte.foust at gmail.com
Wed Mar 27 10:33:12 CDT 2013


That's true in theory, Stuart.  In practice, I've found that some 32-bit
apps have to be specifically run in a compatibility mode that forces the
app to behave.

Charlotte

On Tue, Mar 19, 2013 at 3:01 PM, Stuart McLachlan <stuart at lexacorp.com.pg>wrote:

> Ahem,
>
> Windows 64 bit runs any 32 bit application automatically using WOW64,
>  just as 32 bit
> Windows would run any 16bit (DOS) application using WOW32.
>
> There is no technical reason why you can't run Access97 on Win64.
>
> All of John's problems seem to relate to.
>
> 1.   The known problem with certain font names during installation of A97
> on later versions of
> Windows.
>
> 2.  Problems with the Access security and the absence of System.mdw. This
> is not specific to
> A97, he would have the same problem with A2000 or A2003 if they use Access
> built in
> security and an mdw file.
>
>
>
>
> --
> Stuart
>
> On 19 Mar 2013 at 10:34, Jim Lawrence wrote:
>
> > You are correct John that you can not run a 32 bit application like
> Access97
> > on a 64 bit box without some sort of emulator or virtual drive.
> >
> > If you did get some emulator or VM running then there would be issues
> with
> > the 32 bit drivers that would not be compatible with the environment, the
> > hardware and A97.
> >
> > I would bale on this as it is more effort than it is worth and a solution
> > would never work reliably. The time involved, in such an effort would be
> > better spent re-writing the application.
> >
> > In summary, with a new application there are so many new features that
> can
> > be accessed in this new environment.
> >
> > Jim
> >
>
>
>


More information about the AccessD mailing list