title: Disadvantages of bigger project in VBA
body: <p>i am new in project for company that have bigger enterprise/accounting system based on Visual Basic for Applications (VBA) in Ms Access 97. This application is still alive, they make updates and everything is working relatively fine. But they want to move this app to highest level, speed up development, make this app more "atractive" for end-users and so on.. But i'm not shure if it's good idea to continue developing using this technology (VBA) and therefore
  i have a few questions. I would be very glad if you could help me.</p>
  
  <ol>
  <li>Is VBA even designed for bigger projects? I think, that its more likely for macros and simply functions which extends Access funcionability. </li>
  <li>Will be better to convert the application to .NET winforms/wpf</li>
  <li>Can work more developers on VBA project? </li>
  <li>What are the worst disadvantages of VBA code running in hosting program against stand-alone application? </li>
  <li>Is possible to run unit tests or any similar technology?</li>
  </ol>
  
  <p>Thanks a lot for any response</p>
  
  <p>EDIT:
  Access interface is now using almost agains SQL Server, but that doesn't change main problems.</p>