5 ms·
Once you are going down the road of actually writing code you may as well just take the plunge and use a nicer language than VBA. VBA isn't really going to be
by jiggy2011 13y ago
Once you are going down the road of actually writing code you may as well just take the plunge and use a nicer language than VBA.
VBA isn't really going to be any easier unless you already have visual basic experience in some capacity.
If you use a "proper" database you're also going to get advantages in robustness and ability to easily deploy over a network. My last memories of using access for anything (admittedly about 10 years ago) was that it was prone to performance issues and data loss.
- mattmanser 13y agoIt also doesn't do some extremely basic things properly, e.g. foreign keys. Basically Excel -> Access is easy. Excel -> SQL is easy for a proper programmer. But Excel -> Access -> SQL is a complete nightmare. In the end Excel -> Access is a short-term cheap, long-term very expensive decision. It means you invest a lot of money and effort in a tool that can't do databases properly and can't do forms properly and when you want to move to something that can do either properly you have to do both completely over again without any reusable code as no-one uses anything vaguely resembling VBA any more and Access as a DB that positively encourages the inexperienced to do a lot of things wrong. I am sometimes perplexed why MS hasn't released VBA# yet. It's like there's some petty war that has been going on for the last 7 or 8 years between the office team and the .Net language team.
- regularfry 13y agoBringing proper development tools to Excel is the single biggest thing Microsoft could do to undo decades of damage Excel has caused.