Using NAL to launch split Access database

[Guest]

I have a rather complex situation and am seeking expert advise. My
application has been developed in Access XP, about half of the users within
my primary environment have Access 97 and are not allowed to upgrade. We
launch the application with a NAL (Zen) for these users. The remainder of
the users are external clients who have all updated to Access XP or Access
2003.I don't see any issues with these clients. So my questions relate to the
users in the primary environment.

I now want to split the data from the front end. I understand that the Front
End (FE) should be loaded onto each workstation, will this cause a problem
with my NAL environment? Can the FE be loaded onto the server and accessed
from there?
Can I have a second FE access this data?
Thanks for your response.

 

[Roger Carlson]

If the application was developed in Access XP, your Access 97 users will not
be able to use it. It has nothing to do with NAL. Perhaps I am
misunderstanding.

--
--Roger Carlson
Access Database Samples: www.rogersaccesslibrary.com
Want answers to your Access questions in your Email?
Free subscription:
http://peach.ease.lsoft.com/scripts/wa.exe?SUBED1=ACCESS-L

 

[Chriske911]

I have a rather complex situation and am seeking expert advise. My

application has been developed in Access XP, about half of the users within
my primary environment have Access 97 and are not allowed to upgrade. We
launch the application with a NAL (Zen) for these users. The remainder of
the users are external clients who have all updated to Access XP or Access
2003.I don't see any issues with these clients. So my questions relate to the
users in the primary environment.

I now want to split the data from the front end. I understand that the Front
End (FE) should be loaded onto each workstation, will this cause a problem
with my NAL environment? Can the FE be loaded onto the server and accessed
from there?
Can I have a second FE access this data?
Thanks for your response.

just create a new front for the access 97 users
see to it that the backend part is on a common network share

or distribute the access XP runtime
and set the path to the right access version in your shortcut to start
up the application

there is a diff between the office97 install path and the office XP
install path, the one is just c:\program files\office\msaccess.exe and
the latter will be c:\program files\office11\msaccess.exe
this is only true off course if your company hasn't changed settings
with a custom setup file

distribution with NAL only distributes the application, there is no
need for settings to be distributed since this is already been done
within the access application

only make sure that the backend is made with the oldest version

so create your data backend with access97 in ths case

the XP front won't mind what version is used for the backend as long as
it is older or of the same version

grtz