I have an MS Access application that I've done and would like to convert to
VB.Net. I have a few questions:

1. Is there a conversion routine for this?
2. How hard to convert manually?

Thanks.

If you know ADO then its very simple

How so? Don't I need to convert all the forms?


"Crouchie1998" <(E-Mail Removed)> wrote in message
news:065ED25A-31D6-4579-ABF4-(E-Mail Removed)...
> If you know ADO then its very simple

I think Crouchie is yanking your chain. It's not at all simple or
straightforward because Access works entirely differently than a
VB.NET Windows application. Access was designed over a dozen years
ago, pre-Internet, to be a desktop database application that worked
well on a LAN with users being continuously connected to the data
source. It makes extensive use of the network and hard drive, and does
a lot of the data binding and heavy lifting for you. .NET was designed
primarily with web applications in mind, and is designed to work with
data in a disconnected mode, where data is fetched and stored in a
local cache. Forms need to be hand-crafted, and many common features
found in Access simply aren't there, you have to build them yourself.
Syntactically VB.NET isn't that much of a stretch from VBA, but that's
only the beginning of your learning curve. Because of the drastic
differences between the two platforms, it would be impossible to build
a tool that would automate the process of converting a complex
application for you.

--Mary

On Thu, 17 Mar 2005 15:32:09 -0600, "news.microsoft.com" <(E-Mail Removed)>
wrote:

>How so? Don't I need to convert all the forms?
>
>
>"Crouchie1998" <(E-Mail Removed)> wrote in message
>news:065ED25A-31D6-4579-ABF4-(E-Mail Removed)...
>> If you know ADO then its very simple
>

Mary, Your explanation is vey much appreciated. I guess it's about time for
me to learn .NET and rewrite this app to run under it. Thanks.



"Mary Chipman [MSFT]" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> I think Crouchie is yanking your chain. It's not at all simple or
> straightforward because Access works entirely differently than a
> VB.NET Windows application. Access was designed over a dozen years
> ago, pre-Internet, to be a desktop database application that worked
> well on a LAN with users being continuously connected to the data
> source. It makes extensive use of the network and hard drive, and does
> a lot of the data binding and heavy lifting for you. .NET was designed
> primarily with web applications in mind, and is designed to work with
> data in a disconnected mode, where data is fetched and stored in a
> local cache. Forms need to be hand-crafted, and many common features
> found in Access simply aren't there, you have to build them yourself.
> Syntactically VB.NET isn't that much of a stretch from VBA, but that's
> only the beginning of your learning curve. Because of the drastic
> differences between the two platforms, it would be impossible to build
> a tool that would automate the process of converting a complex
> application for you.
>
> --Mary
>
> On Thu, 17 Mar 2005 15:32:09 -0600, "news.microsoft.com" <(E-Mail Removed)>
> wrote:
>
> >How so? Don't I need to convert all the forms?
> >
> >
> >"Crouchie1998" <(E-Mail Removed)> wrote in message
> >news:065ED25A-31D6-4579-ABF4-(E-Mail Removed)...
> >> If you know ADO then its very simple
> >
>