Robert L. Stewart
robert at webedb.com
Fri Aug 10 08:02:59 CDT 2007
Rocky, Actually, for that kind of money, your install script should detect and "compatible" version of Access. And, if it is not there, install the runtime. Robert At 07:44 PM 8/9/2007, you wrote: >Date: Thu, 9 Aug 2007 17:28:38 -0700 >From: "Rocky Smolin at Beach Access Software" <rockysmolin at bchacc.com> >Subject: Re: [AccessD] Access 2007 run time on same machine with 2003 >To: "'Access Developers discussion and problem solving'" > <accessd at databaseadvisors.com> >Cc: 'Jack Stone' <jack.stone at solidcounsel.com> >Message-ID: <00ea01c7dae5$65528020$0301a8c0 at HAL9005> >Content-Type: text/plain; charset="us-ascii" > >Thanks Doug. That's why I'm a big fan of obsolete technology. It works. > >The client and I are trying to decide whether to standardize on A2007 for >the development of his product. There are some distinct advantages. Or >standardize on something earlier - right now it's compatible with A2000. >Not sure we need to go back that far however. > >The target market for this product is *likely* to have Office Pro but not >for certain. So we're considering a run-time version as well. > >However, since the product t will be selling for 5 figures, it might be >reasonable to require the end user to have Access - some version of it. > >Opinions, anyone? > >TIA > >Rocky