On Sep 5, 8:50 pm, "Tony Toews [MVP]" <tto...@telusplanet.netwrote:
That said I must admit I didn't test it with the A2007 runtime. Famous last words
but I can't see how that'll be a problem.
BTW what improvements would you like to see in the Auto FE Updater?
Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems athttp://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog -http://msmvps.com/blogs/access/
Hi Tony,
Re: AFEU, the only thing I've haven't been able to get to work
consistently is the GUI. Sometimes it's invoked so I can select a ini
file, verify it, and select an icon to use. Other times, it doesn't
appear at all and I edit the ini file as necessary. Not a big deal,
but it does save time and make things a little easier.
Re: Runtime. I think I have it just about figured out except for when
the absolute path is used to point to MSAccess.exe. (Drive Letter
example ini). What would be done in this case - since the client
doesn't have MSACCESS.exe ? Do we point to the Runtime file
somewhere? I haven't seen where this can be done yet.
Where the absolute path is not necessary to define, do we invoke the
Runtime by just using the command switch (\Runtime) by adding it to
the command line (in the ini file). Is it that simple when the client
does not have MS Access?
All my computers have either A2000, A2003, or A2007 installed, so I
haven't been able to test the package on an Access-less computer
yet.
Thanks in advance,
Don