Thanks...I've popped them an email
--
Kevin Hill
President
3NF Consulting
www.3nf-inc.com/NewsGroups.htm
www.DallasDBAs.com/forum - new DB forum for Dallas/Ft. Worth area DBAs.
"Sylvain Lafontaine" <sylvain aei ca (fill the blanks, no spam please)> wrote in message I'm sorry, I never used the runtime engine (even if I always bought the developer edition, I always ask my clients to buy and install the full retail package of Access).
However, the following company is specialised in Access Runtime installation scripts, so they should be able to answer your question at length:
http://www.sagekey.com/ . They also offer in interesting script for installing the Access 2003 runtime without having the client to see the security warning about not signed scripts.
S. L.
In order to avoid purchasing 14 licenses for the users, I am contemplating using my Developer edition of XP to package it up and distribute.
Two questions:
1. Will the runtime engine that is installed mess up the users' ability to use their existing Access 2000 installation for other db work?
2. How easy is it to distribute upgrades to the project I am working on we add features and bug fixes in the runtime scenario?
3. Is it even possible to use Dev edition and ADPs? I've never looked...
--
Kevin Hill
President
3NF Consulting
www.3nf-inc.com/NewsGroups.htm
www.DallasDBAs.com/forum - new DB forum for Dallas/Ft. Worth area DBAs.
"Sylvain Lafontaine" <sylvain aei ca (fill the blanks, no spam please)> wrote in message Yes, there was definitively a big improvement beetween the 2000 and 2002 versions of ADP. Don't forget that ADP 2000 was the very first version of ADP and, as such, was more of a draft than of a mature product.
As to 2002 and 2003, the 2003 version of ADP is virtually identical to the 2002 version because Microsoft is slowly phasing out OLEDB in favor of the .NET framework but that the integration of .NET into Access has to wait for the 2005 version.
Same thing about Data Access Page (DAP). Probably the current version of DAP is also the last one.
S. L.
Thanks! In your experience, is XP a significant improvement over 2000 in the ADP area? I have read it here, and my developer is trying to confirm that Access itself is the source of some issues he is dealing with.
--
Kevin Hill
President
3NF Consulting
www.3nf-inc.com/NewsGroups.htm
"Sylvain Lafontaine" <sylvain aei ca (fill the blanks, no spam please)> wrote in message From my personal experience and the experience of a few friends, there seem to be absolutely no difference beetween ADP XP and 2003: same bugs, with no amelioration but also no degradation and no new bugs. All the changes appears to be cosmetic only and probably with exactly the same work-horse behind.
However, I don't have office 2003 installed right now, as I didn't take the time to install it when I upgraded to a new machine a few months ago; so I don't know if the latest service packs and update for Office 2003, MDAC and Jet change something to that.
As to your client, Office 2003 is probably a better choice than Office 2002 simply because Microsoft will offer security support for a longer period of time; but the menus for Office 2003 are ugly.
S. L.
Just re-read my message and saw my keyboard glitched on me....I meant to ask if you would move from 2000 to XP or 2003. I have read here that XP fixed many 2000 bugs, but did 2003 introduce new ones, or is it more stable than XP?
Thanks!
--
Kevin Hill
President
3NF Consulting
www.3nf-inc.com/NewsGroups.htm
I am finalizing a MDB to ADP conversion using Access XP (2000 format), and running into goofy little bugs that do not appear in XP. If I go to my client and ask him to upgrade the client machines, would you suggest Access or 2003? I have not used 2003 yet, so I am looking to see if they fixed stuff or introduced new problems in that version.
Thanks,
--
Kevin Hill
President
3NF Consulting
www.3nf-inc.com