View Single Post
  #2 (permalink)  
Old November 26th, 2013, 04:15 PM
DougY DougY is offline
Registered User
Points: 18, Level: 1
Points: 18, Level: 1 Points: 18, Level: 1 Points: 18, Level: 1
Activity: 0%
Activity: 0% Activity: 0% Activity: 0%
 
Join Date: Nov 2013
Posts: 6
Thanks: 0
Thanked 0 Times in 0 Posts
Default

Hi Rodger,

It's hard to give you a definitive answer but for a desktop database, VBA will probably ease your pain, and if it won't initially, it should be easier to debug and fix.

Re moving away from Access -- if you already are dabbing in VS12, you can look into re-writing the solution in .Net It will not be as easy and as flowing as Access, but it is the next large step up. However, you should consider the cost involved in developing and maintaining .Net solutions versus Access solutions. I'd recommend trying to work on the Access platform until you have to choose a different tool.
Reply With Quote