2 ms·

You'll also need a 100% compatible MS Access as well - in most cases they are used together. The other key is being able to use all the custom controls etc. Ho

You'll also need a 100% compatible MS Access as well - in most cases they are used together. The other key is being able to use all the custom controls etc. Hopefully, your legacy VB codebase had a fear of NIH and you don't have to worry about this. I've seen a lot of clever systems made in VB, a combination of the developer not knowing any better, and having the perseverance to keep going until they got something that 'worked'.

MisterTea 4y ago
Access was huge. About 6 years ago I had to fix up a predecessors custom data logging program written in VB6 that used an access database. I had to patch a few things to eliminate hard coded paths and a fix for windows 7. First and only time I used VB6 and it was easy to dive into and figure out.