Ms access to vb.net converter free

Viewed 26k times. Thanks in advance. Improve this question. James Ludlow. James Ludlow James Ludlow 1 1 gold badge 4 4 silver badges 22 22 bronze badges. Escaping from MS Access isn't as easy as that. As Albert D. Kallal points out in his lengthy answer below, you'd better fix that first, or no amount of new development in. NET is going to actually address the inherent problems. I'm not sure escaping from many apps is that easy.

Try converting spreadsheets. Add a comment. Active Oldest Votes. Simply rewriting something and moving the functionality over to another platform yields you very little, except spending a lot of money that really doesn't benefit your business of all but hey those developers will take the money, if they convince you of the need of doing this You might want to take a read of this wonderful article by Joel on software Joel by the way developed and created this forum stack overflow — and I was a moderator of some of his discussion forums for almost 10 years ,.

They did it by making the single worst strategic mistake that any software company can make: They decided to rewrite the code from scratch. The fact that the data is already in SQL server helps, but that just might mean that you had the horsepower and capacity and infrastructure to scale something that was poorly designed and the first place A very big major portion of software flexibility comes from having properly normalized data models.

Improve this answer. Grilse 2, 2 2 gold badges 22 22 silver badges 34 34 bronze badges. Albert D. Kallal Albert D. Kallal David: Actually, I'm a software developer, whereas MS Access is a RAD tool designed primarily to allow non-developers to create something useful to them. The very same things that make it good at that also make it bad at the things I value. MS Access is, for a seasoned developer, always the wrong tool. If that makes me a "zealot" in your eyes, so be it.

Life is too short to try to please everyone, and honesty is valuable. Albert: I've seen Excel used as a poor-man's database, too. Doesn't mean we should be poor men. Steven Sudit: you're basically saying I'm not a developer because I develop in Access. This really is bigotry. While of course Access allows non-developers to accomplish a lot, in the hands of an experienced developer it can do much, much more.

If you don't recognize that, it's likely because of ignorance. If it's not, then it's irrational bigotry. Either way, it's not reality-based. Steven Sudit: Albert didn't suggest using Excel in place of Access -- he only suggested that if you take Access away from users, they'll fall back to things like Excel. Do you have any level of reading comprehension at all? Or was that just too much for you to absorb in one go? Access not being a developer tool is just a point of view. If access was not a developer tool then why does Access have Source code control baked into the product?

You think features like VSS source code control support is for non coders and end users? Access is a tool that spans skills from non coders to that of disconnected recordsets and creating of browser neutral web sites on SharePoint, great ribbon development support, and even support for SQL Auzre cloud sql is built into the product.

Show 11 more comments. Steven Sudit Steven Sudit Even though I didn't mention in my answer, I have gone the route of 1 before, but then the application was left that way; i. Mitch: Once the data has been liberated, you have many more options, including mixing and matching UI's.

Courageous answer. Beware the Darth Vaders of the ms-access tag. Hans: I've been bitten by two of the Darths already, so I know what you speak of. Fortunately, I am protected by a strong apathy regarding my SO number. I still don't understand your point. I don't think you have an actual justification for your assertion about "liberation" and you're just trying to make up an after-the-fact justification for saying something silly.

Show 6 more comments. From the technical point of view it is project as any other except few differencies: You have initial database and you always have to be sure that already implemented part in your new solution also have working migration of exisiting data. You have existing UI. Users can like or can hate the UI. Make sure that you understand it so that you create UI which is not worse than existing one.

I created applications where UI had to be completely different and I created applications where UI had to be exactly the same so that users didn't need additional training. Try to add some new features so that new application is reasonable. It is always easier to explain needs for the new application if you can describe new needed features. Ladislav Mrnka Ladislav Mrnka k 57 57 gold badges silver badges bronze badges.

Good points: 1 Don't sell it as a lateral move; always offer new functionality. I think it would be ridiculous to even think of proposing a lateral move -- where's the value in spending all the money and then getting no improvement?

I can't imagine why any department would agree to spend money for any project that did not offer substantially more than what their existing Access app already provided, so the idea that there's something imaginative or innovative about the bright idea of including new features in the port seems ludicrous to me.

What we're looking for though is a massive improvement in being able to effectively support and maintain the application. Have you ever tried to sell a completely lateral move on the base of enhanced ease of support and maintenance? You will get no buyers. Show 3 more comments. Mitch Wheat Mitch Wheat k 42 42 gold badges silver badges bronze badges. I'm with you on the idea of not trying to port the whole thing, but wouldn't it be better to leave the old functionality in place while doing new work in a new platform?

Steven Sudit: That's what I was suggesting obviously not well enough! Mitch, if I understand correctly, where our advice differs is that you recommend porting the basic functionality first, then building on it.

In contrast, I'm saying it might be best to build only new functionality with new tools, forcing the users to keep use MS Access for existing tasks. Mitch, in commenting on Ladislav's answer, I think I figured out what the big difference is. You're talking about replacing an MS Access app with one that initially does less.

This is a hard sell. I decided that we are going to have to go with a conversion tool. As of right now, the price of course is a factor but not as much as getting a real good conversion tool. Would you say that AccessWhiz is one of the better ones out there? If not, could you recommend some real good tools for performing these conversions.

So, what this program does is take an Access mdb file, analyzes it, and then converts all the forms into vb. It even transforms the access data into sql tables and even has a reporting engine that would allow to use the access reports against the new database though I did rewrite them using ActiveReports because I felt it was cleaner that way.

SSMA converts the tables and queries quite well though I have learned just how lazy I am in some cases…. It does not, however, deal with forms, modules, classes, or reports. No Account? Sign up. By signing in, you agree to our Terms of Use and Privacy Policy. Already have an account? Sign in. By signing up, you agree to our Terms of Use and Privacy Policy.

Enter the email address associated with your account. We'll send a magic link to your inbox. Email Address. All Sign in options. MacX YouTube Downloader. Microsoft Office YTD Video Downloader. Adobe Photoshop CC. VirtualDJ Avast Free Security. WhatsApp Messenger. Talking Tom Cat. Clash of Clans. Subway Surfers. TubeMate 3. Google Play. Navient student loan settlement. GameStop in-store PS5 restock. N95, KN95, KF94 masks. Windows Windows. Most Popular.