how to get from an MS Access app to vb.net?

[Deano]

Hi,

I have a finished Microsoft Access app that we are distributing using an
Access runtime. This works fine (mostly) but I'm sold on the advantages of
dot.NET and upgrading to vb.NET seems like a good idea for the future. I'm
also keen to develop new software in vb.NET as soon as possible.
I will work out how to port the app and how to use ado.NET etc, however I'm
not certain about all the things I need to consider hence the questions;

1. Reporting. I will miss Access' report generator. Is there a
recommended third-party app for this? What other arrangements do developers
make when using vb.NET?

2. Deployment/Remote updating of the app. I know from experience that
there is a world of difference between the theory concerting the deployment
of apps and what you actually need to do. How good is dot.NET in this area?
I'd love to develop a windows forms app that could be updated without
sending out a CD etc.

3. Possibly critical differences when moving from Access. I read that
there aren't any subforms in dot.NET or windows forms. Is this right? Does
the mainform/subform concept exist in some way? I have important forms that
depend on this and I can't see a way around this. Does anyone know of any
other issues when moving from Access to dot.NET apart from recoding etc?

4. User data. My app allows the user to back up and restore the data they
have created. Is this fairly straightforward process once I become familiar
with ado.NET?

The app is confined to working on the user's pc and no server elements are
involved.

Many thanks for any comments, links etc (I have done a fair amount of
research on Google Groups but Access-related posts are at a minimum or ask
for something that converts code to dot.NET).

regards
Martin