I have written an application in Microsoft Access which works fine for what we want at the moment. The problem is we have a number of satellite offices which will need to access the database. I am therefore going to move the database onto SQL Server as step one, and carry on using Access as the front end until the database has settled in.
In order to roll it out to the other offices I have a number of questions:
1) If the Access database is installed at each office locally with a connection to the SQL server over the VPN can I expect a reasonable performance? I assume because all the forms, etc are local then only the data would be transferred over the VPN. Issues arise, I guess, when (for example) the user is browsing through a dataset using a single form with record navigators, would Access grab the whole dataset or just fetch each record as it was being viewed? I understand this might not be an ideal solution but from a business viewpoint Access is so fast to develop in it would be the ideal choice.
2) The other option I have come up with is to write a front-end application in VB/C++/C# which would connect to the SQL database and could be written in such a way that it wouldn't ask for large data sets in one go. VB would be the obvious choice for me as I have a lot of experience of VBA and the transition would be fairly painless. Although when I have worked with VB in the past it does seem a bit fiddly when it comes to handling databases (particularly when compared with Access).
So, in summary, am I better continuing with Access or using a devlopment tool. If so which would be the best VB, C++ or C#?