Francisco Tapia
fhtapia at gmail.com
Thu Aug 25 02:40:53 CDT 2005
another method for distribution and not worrying about what version your user have is to deploy your mde with a runtime. This way you can ensure that your db will work fine. W/ the latest sagekey scripts (wise installer). it is possible to deploy a runtime A) doesn't need the digital certificate and B) it keeps context menus for importing and exporting data for merging w/ excel/word. of course there's the added benefit w/ sage that you won't have to worry about a user haveing their install conflict w/ an existing Access version on the users machine. On 8/18/05, Joe Hecht <jmhecht at earthlink.net> wrote: > > So I should write in XP and then port up to 2K3. > Ten user would need to select proper version for their system. > > Or start in 2K3 and go down to XP. > > I would have 2 mde files of same app. > > -----Original Message----- > From: accessd-bounces at databaseadvisors.com > [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Stuart > McLachlan > Sent: Wednesday, August 17, 2005 11:10 PM > To: Access Developers discussion and problem solving > Subject: Re: [AccessD] MDE question > > On 17 Aug 2005 at 21:53, Joe Hecht wrote: > > > If I do an app in Access 2K3 and make an .mde out if it will older > versions > > of Access be able to use it? > > > > No, and future versions probably won't be able to either - at least that's > been the case up to now. > > > > > -- > Stuart > > > -- > AccessD mailing list > AccessD at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/accessd > Website: http://www.databaseadvisors.com > > -- > AccessD mailing list > AccessD at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/accessd > Website: http://www.databaseadvisors.com > -- -Francisco http://pcthis.blogspot.com |PC news with out the jargon! http://sqlthis.blogspot.com | Tsql and More...