Jim Dettman
jimdettman at verizon.net
Mon Nov 14 12:05:19 CST 2011
Always been that way all the way back to day 1. When you use the runtime version, your using the same MSACCESS.EXE and everything else. In fact you can take the full version and start it with the /runtime switch to get a runtime environment. Prior to Windows 95, it wasn't done via registry, but it was still the same .EXE Jim. -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of jwcolby Sent: Monday, November 14, 2011 12:21 PM To: Access Developers discussion and problem solving Subject: Re: [AccessD] Access 2010 Deployment (cross posted) What I have read is that the runtime is the full version with registry entries which lobotomize it. John W. Colby Colby Consulting Reality is what refuses to go away when you do not believe in it On 11/14/2011 11:52 AM, Mark Simms wrote: > Sorry, I cannot answer this directly. > But one huge issue is: has the run-time version kept-up with all of the > fixes to the full version ? > > Hopefully, MSFT engineers just have 2 separate solutions that share the same > code base....and all they have to do is recompile to sync the runtime with > the full. I'm not sure of that however. > > > -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com