Migrating from VBA to VB.net
i have a database with a lot of functionality
that I want to migrate to VB.net .
Are there any resources you could point me to?
that I want to migrate to VB.net .
Are there any resources you could point me to?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
yes, I am intimately familiar with Access databases developed in EXACTLY that manner. And those Access applications DO NOT stand a snowball's chance in H**L of being viable candidates for upgrade to VB.NET. Trust me, you will create a MONSTER if you attempt to upgrade this Access app (VBA) to VB.NET, and that monster will be will EAT YOU alive, attempting to make it work. You will waste far more time attempting to get this thing to come close to functioning than it would take you to start from scratch, learn the correct way to do things, and write the new VB.NET app to replace this existing Access application.
I AM a developer by trade, and I have been building Access applications that are 100% Object Oriented (for instance, I NEVER EVER use bound controls, but write internal VBA classes to encapsulate all of the business rules, and to manage the movement of data to and from the tables), for more than 10 years. I also develop VB6 and VB.NET apps, so I know whereof I speak. Please do yourself a favor, and either learn to write code properly in .NET yourself, or pass this project to someone who can.
I hate to be blunt, but I am trying to make this very plain and straightforward for you.
AW
I AM a developer by trade, and I have been building Access applications that are 100% Object Oriented (for instance, I NEVER EVER use bound controls, but write internal VBA classes to encapsulate all of the business rules, and to manage the movement of data to and from the tables), for more than 10 years. I also develop VB6 and VB.NET apps, so I know whereof I speak. Please do yourself a favor, and either learn to write code properly in .NET yourself, or pass this project to someone who can.
I hate to be blunt, but I am trying to make this very plain and straightforward for you.
AW
ASKER
and interface with It people and I don't know if you're familiar with the
little access database thron together haphazardly that becomes a mission critical application
without you even noticing and taking time from day to day operations in maintenance.
This is my case and The reason for my wanting to go to vb .net is that maintenance is taking too much
time.