Getting started VB6 to .Net

[Doug T.]

OK. Just ordered VS2005 Pro. to make the transition from VB6.

A commercial application needs to be converted from VB6. Currently it is a
multi-formed app that communicates to an many-tabled Access db. Stores and
keeps track of appointments, people, pictures, etc. Also allows two users to
communicate changes to each other using a proprietary db sync (track changes
from user 1, send by email, then user 2 will import the information and vise
versa.)

I think this application just screams ".NET" But here is where I need help.
I anticipate having 100 to 5000 users, each with a few sub-accounts. I want
the sub-accounts to be able to communicate, without seeing other user's data.
Most apps that I see in .Net allow everyone to see all the data. (OK, just
add a userid and select only these userid records then.) I am sure that
there are other pitfalls and shortcuts to this. Any comments would be
appreciated.

[Andrew Robinson]

First couple of questions:

1. Do you want to creat a web (asp.net) app or a windows forms app?
2. Would you consider using SqlExpress instead of Acess?

-Andrew

"Doug T." <Do***@discussions.microsoft.com> wrote in message
news:40**********************************@microsof t.com...

OK. Just ordered VS2005 Pro. to make the transition from VB6.

A commercial application needs to be converted from VB6. Currently it is
a
multi-formed app that communicates to an many-tabled Access db. Stores
and
keeps track of appointments, people, pictures, etc. Also allows two users
to
communicate changes to each other using a proprietary db sync (track
changes
from user 1, send by email, then user 2 will import the information and
vise
versa.)

I think this application just screams ".NET" But here is where I need
help.
I anticipate having 100 to 5000 users, each with a few sub-accounts. I
want
the sub-accounts to be able to communicate, without seeing other user's
data.
Most apps that I see in .Net allow everyone to see all the data. (OK, just
add a userid and select only these userid records then.) I am sure that
there are other pitfalls and shortcuts to this. Any comments would be
appreciated.

[Doug T.]

Q1. Do you want to creat a web (asp.net) app or a windows forms app?
A1. I think asp.net would be great, but I cannot assume that all users have
internet access all the time. I would be better if the data is local until
the user "syncs" the data.

Q2. Would you consider using SqlExpress instead of Acess?
A1. Backend should not matter, ADO should work.

DT

"Andrew Robinson" wrote:

First couple of questions:

1. Do you want to creat a web (asp.net) app or a windows forms app?
2. Would you consider using SqlExpress instead of Acess?

-Andrew

"Doug T." <Do***@discussions.microsoft.com> wrote in message
news:40**********************************@microsof t.com...

OK. Just ordered VS2005 Pro. to make the transition from VB6.

A commercial application needs to be converted from VB6. Currently it is
a
multi-formed app that communicates to an many-tabled Access db. Stores
and
keeps track of appointments, people, pictures, etc. Also allows two users
to
communicate changes to each other using a proprietary db sync (track
changes
from user 1, send by email, then user 2 will import the information and
vise
versa.)

I think this application just screams ".NET" But here is where I need
help.
I anticipate having 100 to 5000 users, each with a few sub-accounts. I
want
the sub-accounts to be able to communicate, without seeing other user's
data.
Most apps that I see in .Net allow everyone to see all the data. (OK, just
add a userid and select only these userid records then.) I am sure that
there are other pitfalls and shortcuts to this. Any comments would be
appreciated.

[Norman Yuan]

Be aware that moving VB6 APP to .NET app (whether it is web app or win form
app) most likely means "re-writing". Classical VB is so different from .NET
(#C or VB.NET), especially, when it is database app: ADO.NET is completely
different from ADO in VB6 on concept level (sure, you can still use ADO
(classical) in .NET app, but then why convert it?).

It only makes sense to re-do the app in .NET if you have a long wish list of
improvement for that app and the ROI (return of investment) is worth doing
it.

"Doug T." <Do***@discussions.microsoft.com> wrote in message
news:40**********************************@microsof t.com...

OK. Just ordered VS2005 Pro. to make the transition from VB6.

A commercial application needs to be converted from VB6. Currently it is
a
multi-formed app that communicates to an many-tabled Access db. Stores
and
keeps track of appointments, people, pictures, etc. Also allows two users
to
communicate changes to each other using a proprietary db sync (track
changes
from user 1, send by email, then user 2 will import the information and
vise
versa.)

I think this application just screams ".NET" But here is where I need
help.
I anticipate having 100 to 5000 users, each with a few sub-accounts. I
want
the sub-accounts to be able to communicate, without seeing other user's
data.
Most apps that I see in .Net allow everyone to see all the data. (OK, just
add a userid and select only these userid records then.) I am sure that
there are other pitfalls and shortcuts to this. Any comments would be
appreciated.