2009 anybody?

I have been using it. The big draw is supposed to be speed. I am finding the user interface is a bit more jerky than 2008. I haven't gotten to any big assemblies or parts yet.

It hasn't crashed yet.

The standalone rendering package is pretty neat.

There is a lot of new/changed stuff in the API and the API help. Seems like they are moving away from VBA and hence from user friendliness. The API help is not as straightforward as it was before at least for non-programmers. Another round of redoing old macros.

TOP

If they are moving away from VBA, what are they moving to?

Asking as a non programmer who has recently decided to maybe, possibly, perhaps think about learning to play with the API.

John Layne

-- Posted on news://freenews.netfront.net - Complaints to snipped-for-privacy@netfront.net --

For now VBA6 is still supported but they are making it pretty clear that VB.NET, C#, C++ and a few other flavors are the way to go in the future. There are subtle differences between VBA6 and VB.NET. You can edit/record macros in C# I believe.

The way the objects are handled has changed. The naming of some common ones has changed. The changes would have more meaning to a programmer than to you or I.

TOP