A2K Runtime conflict with A97 on a network ?

[Bruno Frisque]

Hi,.
After the Installation of a MDE Runtime (A2K) on a station having Access97
installed, there are 2 error messages.

- Workgroup Administrator couldn't create the workgoup information file. ..
err -3100
After pressing OK :
- error : couldn't find file '##' (two little squares). This file is
required for startup.

The question is :
As the user doesn't know if any serurity was implemented in his old A97,
should it be possible that this fact jeopardise a brand new A2K Runtime ??

If yes removing Access97, reinstalling A97 and the A2K run time should solve
the problem ?

Many thanks in advance

 

[david epsom dot com dot au]

Perhaps your user does not have adequate permission
for where Access wants to put or expects to see the
workgroup information file. Did you include a workgroup
information file with the build? Is it referenced
by the shortcut?

(david)

 

[Bruno Frisque]

Thanks for answering.
The user said I had full administrator privilege at the time of Runtime
installation.
Yes the err msg said : 'cannot create the Workgroup information file .. err
3100'
Why ??
My application do not have any security on it.
And as far as the user remembers no security was implemented in their Access
97.
(they need to keep A97 for an old program)

It should be easy to rejoin the system.mdw via Security etc .. but these
options do not exist with a runtime ..
Any other way to solve this issue ??
Thanks again

 

[david epsom dot com dot au]

There is no conflict with A97.


A workgroup information file is required.

Normally the A2K workgroup information file
goes to c:\program files\common files\system,
but it could be somewhere else.

Is there a workgroup information file in
c:\program files\common files\system?

Did you include a workgroup information file with the build?
I would expect the runtime installation to create a
workgroup information file if none exists, but I have
not tried that.


(david)