I can only share my own experience on this, be warned I am no expert.
I looked a different ways of doing this and finally settled on providing access through asp via a webserver which I set up in the office, to date it has worked very very well and I am very pleased with it. There are benefits as well to this type of access, using a web browser means it's cross platform but the bigger advantage over deploying a remote application to your clients is that when you want to make changes or updates you just need to make them on the server. We only have a standard UK broadband connection and it works fine, though we never have more than about 3 remote clients connected at once, I am not sure how many connection a set up like this can handle, perhaps somebody else on the forum could comment. To do it properly you will need a static IP address, although we don't have one instead we use DYNU.COM to resolve ours (once again this has served our purpose fine). Of course you don't have to use asp to connect in this way, you could use PHP, JS or aspx (asp.net). If you choose this method there are litteraly hundreds of free tutorials on the www and if you have reasonably solid grounding in access you will have little trouble tackling them.
The other way of course would be to create standalone application using vb or similar and utilise com control, I really don't know much about this except that there are several issues associated with this control and I also belief it is quite resource hungry (though don't quote me). You may also need to set up some sort of virtual network as well to use this method securely. I understand that .net is the way forward if you take this road (does not use com), though this might just be a microsoft advertising ploy, perhaps one of the .net guru's could comment.
There may be other methods these are the ones that I explored.
I replied as no one else had, I hope it helps a little and steers you in the right direction. Postback if you want any more info.
Keith
