Doug Murphy
dw-murphy at cox.net
Tue Nov 12 14:32:05 CST 2013
It is alive and well, http://msdn.microsoft.com/en-us/vstudio/ff796201.aspx. -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Arthur Fuller Sent: Tuesday, November 12, 2013 12:10 PM To: Access Developers discussion and problem solving Subject: Re: [AccessD] Poll: Question for Access Developers Shamil, I thought that LightSwitch was declared dead by MS. Perhaps I'm wrong. Arthur On Tue, Nov 12, 2013 at 1:46 PM, Salakhetdinov Shamil <mcp2004 at mail.ru>wrote: > Hi Arthur -- > > Access 1.0 - 2007 compiler, converting mdbs with VBA modules into > VB.NET/C# sources, compiling them into DLLs and linking with > .NET-based runtime engine (EXEs and DLLs) would be useful I suppose. > VBA as it's now - is 'evil' (I mean not VBA language but its unstable > for 'legal tricks' engine) - it should be substituted with VB.NET/C#, > or interpreted using VB.NET/C# based new engine. > In theory such a compiler compiling into .NET exe can be done (I do > not see any technical obstacles) as the current version of VB.NET/C# > covers VB6/VBA (including dynamic binding, eval etc.) - actually > current versions of VB.NET and C# have much more powerful and very > effectively working late binding VB6/VBA have never had. All the MS > Access 1.0-2007 functionality can be programmed/interpreted by using VB.NET/C#... > > In practice I think Visual Studio LightSwitch ( > http://msdn.microsoft.com/en-us/vstudio/ff796201.aspx ) is going to > occupy the niche of "MS Access 1.0-2007 compiler". So the chances of > "MS Access 1.0 - 2007 exe compiler" to appear are very low. I'd be > happy if I'd be found wrong with my last statement. > > Thank you. > > -- Shamil > > > -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com