[AccessD] Office 2007 and .Net

For engineering apps, it's best to go with pure C/C++ and interface to Excel
via DLL.
The DLL effectively replaces slower VBA code.
I believe the DLL could be built using Visual Studio and the dot-net
platform,
 but of course the CLR will be required.

Here is a nice product that may just be the ticket:
http://www.calc4web.com/
Code in Excel, execute native DLLs.

What they are asking for is a pipedream IMHO.
> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com
> [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Drew Wutka
> Sent: Wednesday, April 22, 2009 1:56 PM
> To: Access Developers discussion and problem solving
> Subject: Re: [AccessD] Office 2007 and .Net
>
> LOL.
>
> There is a good reason for that.... they aren't programmers.
> They are engineers who are fiddling with programming.
>
> So while they are more then able to use the programming
> tools, they are relative newbies, and hopelessly addicted to
> excel...LOL.  I talked with someone that is somewhat involved
> with this, and he is going to look into having the group meet
> with me to discuss OOP a bit, and see if I can steer them
> away from a train wreck.  What they are doing could be a
> really awesome system, but it could very easily end up being
> a total wreck!
>
> Drew
>
> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com
> [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of
> Susan Harkins
> Sent: Wednesday, April 22, 2009 12:16 PM
> To: Access Developers discussion and problem solving
> Subject: Re: [AccessD] Office 2007 and .Net
>
> > The other day, someone asked me when we are planning on moving our
> > company to Office 2007. Right now, we have no real plans to
> do so.  We
> > are currently using Office 2003.  The people that were asking are
> using
> > Visual Studio 2005, to work on a custom project.  They want
> to be able
> > to use Excel to test their code.  More specifically, they
> want to take
> > the code from Visual Studio (I believe they are coding in
> VB.NET), and
> > paste it into an Excel macro to test it......
>
> =====I can't help but ask why? If they're developing a custom
> project, why can't they test their code in its own .exe file?
>
> Susan H.
>
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com The information
> contained in this transmission is intended only for the
> person or entity to which it is addressed and may contain
> II-VI Proprietary and/or II-VI Business Sensitive material.
> If you are not the intended recipient, please contact the
> sender immediately and destroy the material in its entirety,
> whether electronic or hard copy.
> You are notified that any review, retransmission, copying,
> disclosure, dissemination, or other use of, or taking of any
> action in reliance upon this information by persons or
> entities other than the intended recipient is prohibited.
>
>
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>