access and vsto

  • Thread starter Thread starter JohnE
  • Start date Start date
J

JohnE

Hello. This primarily a general question that I am wondering about. Has
anyone used VSTO (with Visual Studio) to "convert" (lack of a better word) an
Access application? If so, how did it go? Did it take long based on the
size of the mde (or mdb)? Any pitfalls to be aware of?

Thanks for your time.

.... John
 
You mean like creating a runtimeversion? When using VSTO you can just use a
wizard for that. Pitfalls won't be there only when pitfalls were created by
the developer. I didn't like the fact that you had to purchase vsto just for
creating runtimes. I think a lot of people thought so to regarding the fact
that it is back for free again. If that's what you were referring to than
that's my 2 cents about it. If you are talking about some other conversion I
haven't got a clue what you are converting to.
 
"back for free again"? The current version is the first version of the
runtime to be free: all previous versions cost money.

Note that no conversion is done: packaging the application for distribution
does not change the application in any way, shape or form. All you're doing
is packaging your existing application along with the runtime. You need to
ensure that the application will run properly with the runtime. There's good
information to be found at the Microsoft Access (Office) Developer Edition
FAQ that Tony Toews maintains at
http://www.granite.ab.ca/access/developereditionfaq.htm
 
Ha, thanks for correcting me on that one Doug. I have the office dev. tools
from the previous versions. Ofcourse this was paid for by my boss. I guess in
the end you don't see what your boss pays for anymore. ;-)
 
Back
Top