M
mat
A project that was going to be installed on win2003 TS with Access
retail will instead be installed using the Access 2003 runtime on
Citrix. I've used the sagekey script for several installs but not too
many times on TS and never on Citrix. It's a sudden change and they've
given me little time to adapt.
The app uses sql server 2005 for the data side and we'll configure odbc
for that. The app will be distributed as an mde.
The server will be a VM, and there will be no other copies of Access
installed (ie no access retail installs on this virtual box).
I have little experience with the Access 2007 runtime but I think it
might 'run' this app also? If it stripped the toolbars it's be a hard
switch to make. Also I may not need to use the sagekey script; it's been
useful for installs in more mixed environments, where other copies of
Access may be installed, but that condition won't arise here. I just
mean to say, this does not have to be Access 2003 runtime plus sagekey;
it just needs to work with a minimum of fuss.
All of my apps utilize distinct copies of the mdb/mde for each user. I
have a good system worked out for automated updates, so it's easy to
distribute updates to the front end file. I know Tony Toews Auto FE
Updater has some smarts about Citrix, but there is little detailed info
on the site about what that might mean. I'd not be eager to switch out
my FE updating system for Tony's, which I've tried and like, but prefer
my own.
I don't have any sustantial recent exposure to citrix. They will be
using presentation manager (I think one ver back from current PM), so
the app will be 'served', and the users won't see a regular RD desktop
on the server. I am not sure what measures I need to take to make the
install work well with citrix PM.
I'm also not sure what is the most foolproof approach to take as far as
installation directories...this may be related to Citrix too. This is
what I am guessing at the moment, but would appreciate any input.
An admin will want to install the first instance of the application;
that will of course include the Access 2003 runtime.
The other users need to get a dedicated copy of the front end mde and
have citrix wired up to offer that as a published application. Does that
mean that citrix creates a copy of the mde for each user? I've read that
bat files are involved with citrix Access installs that use dedicated
front ends but have no detail; I suppose that's to create a distinct
copy of the mde? Does one use the my docs folder, or the local settings
\application data folder? The user needs full perms on that dir of
course.
I have read around on this topic and there is little published. Tony's
site is good, but the 'excellend article' it refs is very old, and
Tony's site is thin on details of the kind I need, esp re runtime and
citrix.
retail will instead be installed using the Access 2003 runtime on
Citrix. I've used the sagekey script for several installs but not too
many times on TS and never on Citrix. It's a sudden change and they've
given me little time to adapt.
The app uses sql server 2005 for the data side and we'll configure odbc
for that. The app will be distributed as an mde.
The server will be a VM, and there will be no other copies of Access
installed (ie no access retail installs on this virtual box).
I have little experience with the Access 2007 runtime but I think it
might 'run' this app also? If it stripped the toolbars it's be a hard
switch to make. Also I may not need to use the sagekey script; it's been
useful for installs in more mixed environments, where other copies of
Access may be installed, but that condition won't arise here. I just
mean to say, this does not have to be Access 2003 runtime plus sagekey;
it just needs to work with a minimum of fuss.
All of my apps utilize distinct copies of the mdb/mde for each user. I
have a good system worked out for automated updates, so it's easy to
distribute updates to the front end file. I know Tony Toews Auto FE
Updater has some smarts about Citrix, but there is little detailed info
on the site about what that might mean. I'd not be eager to switch out
my FE updating system for Tony's, which I've tried and like, but prefer
my own.
I don't have any sustantial recent exposure to citrix. They will be
using presentation manager (I think one ver back from current PM), so
the app will be 'served', and the users won't see a regular RD desktop
on the server. I am not sure what measures I need to take to make the
install work well with citrix PM.
I'm also not sure what is the most foolproof approach to take as far as
installation directories...this may be related to Citrix too. This is
what I am guessing at the moment, but would appreciate any input.
An admin will want to install the first instance of the application;
that will of course include the Access 2003 runtime.
The other users need to get a dedicated copy of the front end mde and
have citrix wired up to offer that as a published application. Does that
mean that citrix creates a copy of the mde for each user? I've read that
bat files are involved with citrix Access installs that use dedicated
front ends but have no detail; I suppose that's to create a distinct
copy of the mde? Does one use the my docs folder, or the local settings
\application data folder? The user needs full perms on that dir of
course.
I have read around on this topic and there is little published. Tony's
site is good, but the 'excellend article' it refs is very old, and
Tony's site is thin on details of the kind I need, esp re runtime and
citrix.