Upgrading Access 97 application to dotNet

[kavsak]

Hi. Not sure that this is the right place to ask but here goes.

I have an application based on access97 and VB6 which I need to
upgrade. It has to handle up to 20 concurrent users on a Win2k network
( to be upgraded to XP next year) which has no connection to the
outside world, but normally there are no more than 2. It has
approximately 150 tables with complicated validation rules and a large
amount of calculation. I want to rewrite it in VB net or C# with a
suitable modern database. So I far I have 3 weeks experience of the
..Net world.

I am not permitted to run any form of central database server, but data
tables must (?) be held on the network server to provide the multi user
capability. It must also be possible to transfer the application and
its database to a standalone laptop for use in other locations.

Can I use SQL Server in any form as this seems to be the best match for
VS2005 or do I have to continue to use Access?

Any advice on the best way to proceed would be most welcome.

Thanks in advance.

[Tim Patrick]

You can certainly use SQL Server for your data storage, but it may conflict
with your requirement that no "form of central database server" be used.
SQL Server is a database server, as its name implies. Perhaps you mean that
there will not be a machine set up that is solely dedicated to managing the
database. SQL Server can be installed on any workstation and made available
to other users. It sounds like your data interaction needs are simple, so
this should work.

There are some syntax differences between Access SQL and SQL Server SQL,
but you will probably learn and correct those pretty quickly. Also, there
is a little more administration involved in a SQL Server database; it's not
just a single file like Access. But still, give thanks that you aren't considering
Oracle (20MB minimum client-side install with hundreds of files. Boo. Hiss.)

VB2005 includes an "upgrade wizard" that will convert your VB6 program to
VB2005. It doesn't do a complete job, and sometimes not even a great job.
But it will give you a start over writing it from scratch.

I have a book that deals with developing database applications in VB2005
(see my signature below). But if your focus is on the database side, you
may also want to consider the many good books by Bill Vaughn (the "Hitchhiker "
guides).

-----
Tim Patrick - www.timaki.com
Start-to-Finish Visual Basic 2005

Hi. Not sure that this is the right place to ask but here goes.

I have an application based on access97 and VB6 which I need to
upgrade. It has to handle up to 20 concurrent users on a Win2k network
( to be upgraded to XP next year) which has no connection to the
outside world, but normally there are no more than 2. It has
approximately 150 tables with complicated validation rules and a large
amount of calculation. I want to rewrite it in VB net or C# with a
suitable modern database. So I far I have 3 weeks experience of the
.Net world.

I am not permitted to run any form of central database server, but
data tables must (?) be held on the network server to provide the
multi user capability. It must also be possible to transfer the
application and its database to a standalone laptop for use in other
locations.

Can I use SQL Server in any form as this seems to be the best match
for VS2005 or do I have to continue to use Access?

Any advice on the best way to proceed would be most welcome.

Thanks in advance.

[kavsak]

Thanks for the prompt reply, but I really do mean that there can be no
server. Using someone elses workstation is not an option either.
Central data storage and individual database engines are mandated.
There is a very large amount of paranoia in this grey suited
organisation.

[Tim Patrick]

Gee, this doesn't sound like a technology issue.

SQL Server does run as a service, not as an application like Access, or as
an extension of your own program like OLE DB and the like. SQL Server Express
does have a mode that lets you access an MDF file (similar to an MDB file)
directly instead of through the normal server-based methods, but I don't
know if that method would support multiple users. I've never used that file-based
method, and I think it only applies to the Express version of the product.

VB2005 continues to support Access just fine, so you're free to continue
with that data source.

-----
Tim Patrick - www.timaki.com
Start-to-Finish Visual Basic 2005

Thanks for the prompt reply, but I really do mean that there can be no
server. Using someone elses workstation is not an option either.
Central data storage and individual database engines are mandated.
There is a very large amount of paranoia in this grey suited
organisation.

[aaron.kempf]

you should just migrate it to Excel.

the fucking retards at your company are obviously retarded

-Aaron

Tim Patrick wrote:

Gee, this doesn't sound like a technology issue.

SQL Server does run as a service, not as an application like Access, or as
an extension of your own program like OLE DB and the like. SQL Server Express
does have a mode that lets you access an MDF file (similar to an MDB file)
directly instead of through the normal server-based methods, but I don't
know if that method would support multiple users. I've never used that file-based
method, and I think it only applies to the Express version of the product.

VB2005 continues to support Access just fine, so you're free to continue
with that data source.

-----
Tim Patrick - www.timaki.com
Start-to-Finish Visual Basic 2005

Thanks for the prompt reply, but I really do mean that there can be no
server. Using someone elses workstation is not an option either.
Central data storage and individual database engines are mandated.
There is a very large amount of paranoia in this grey suited
organisation.

[RobinS]

You *could* put a SQLServer database out there and use it.
This is from a post by David Browne back in mid-November; he said
you could use SQLServer express for multiple users. These are the
restrictions.

-----
SQL Server Express is well suited to small workgroup environments.
It has no connection limit or workload governer. Rather it is physically
limited to 1CPU, 1GB of RAM and 4GB per database. By default the installer
doesn't enable remote connections to the database, but that's just to be
"secure by default". You can enable remote connections after the install
and you're good to go.
-----

However, I have to admit, I'd probably use Access, because it's so easy
to manage (assuming the database isn't huge).

Robin S.
-----------------------------

"Tim Patrick" <in*****@invali d.com.invalidwr ote in message
news:e3******** *************** **@newsgroups.c omcast.net...

Gee, this doesn't sound like a technology issue.

SQL Server does run as a service, not as an application like Access, or as
an extension of your own program like OLE DB and the like. SQL Server
Express does have a mode that lets you access an MDF file (similar to an
MDB file) directly instead of through the normal server-based methods, but
I don't know if that method would support multiple users. I've never used
that file-based method, and I think it only applies to the Express version
of the product.

VB2005 continues to support Access just fine, so you're free to continue
with that data source.

-----
Tim Patrick - www.timaki.com
Start-to-Finish Visual Basic 2005

>Thanks for the prompt reply, but I really do mean that there can be no
server. Using someone elses workstation is not an option either.
Central data storage and individual database engines are mandated.
There is a very large amount of paranoia in this grey suited
organisation .

[aaron.kempf]

Robin;

no wonder you're such a VB crybaby.. lol

You're an Acccess wannabe programmer!

RobinS wrote:

You *could* put a SQLServer database out there and use it.
This is from a post by David Browne back in mid-November; he said
you could use SQLServer express for multiple users. These are the
restrictions.

-----
SQL Server Express is well suited to small workgroup environments.
It has no connection limit or workload governer. Rather it is physically
limited to 1CPU, 1GB of RAM and 4GB per database. By default the installer
doesn't enable remote connections to the database, but that's just to be
"secure by default". You can enable remote connections after the install
and you're good to go.
-----

However, I have to admit, I'd probably use Access, because it's so easy
to manage (assuming the database isn't huge).

Robin S.
-----------------------------

"Tim Patrick" <in*****@invali d.com.invalidwr ote in message
news:e3******** *************** **@newsgroups.c omcast.net...

Gee, this doesn't sound like a technology issue.

SQL Server does run as a service, not as an application like Access, or as
an extension of your own program like OLE DB and the like. SQL Server
Express does have a mode that lets you access an MDF file (similar to an
MDB file) directly instead of through the normal server-based methods, but
I don't know if that method would support multiple users. I've never used
that file-based method, and I think it only applies to the Express version
of the product.

VB2005 continues to support Access just fine, so you're free to continue
with that data source.

-----
Tim Patrick - www.timaki.com
Start-to-Finish Visual Basic 2005

Thanks for the prompt reply, but I really do mean that there can be no
server. Using someone elses workstation is not an option either.
Central data storage and individual database engines are mandated.
There is a very large amount of paranoia in this grey suited
organisation.

[Cor Ligthert [MVP]]

RobinS and Patrick,

Do you think that it is helpful to show people a wrong way of use of tools.

kavsaks organisation is obvious afraid that he build applications in his
organisation and now we are helping to brake those rules with all kind of
bad advices.

He just need to get his application running on his central organisation
server. If not, then the organisation does not need his application.

Just my idea maybe not so well written but I hope you understand what I want
to say. If not I will repeat it.

Cor

"RobinS" <Ro****@NoSpam. yah.noneschreef in bericht
news:kL******** *************** *******@comcast .com...

You *could* put a SQLServer database out there and use it.
This is from a post by David Browne back in mid-November; he said
you could use SQLServer express for multiple users. These are the
restrictions.

-----
SQL Server Express is well suited to small workgroup environments.
It has no connection limit or workload governer. Rather it is physically
limited to 1CPU, 1GB of RAM and 4GB per database. By default the
installer
doesn't enable remote connections to the database, but that's just to be
"secure by default". You can enable remote connections after the install
and you're good to go.
-----

However, I have to admit, I'd probably use Access, because it's so easy
to manage (assuming the database isn't huge).

Robin S.
-----------------------------

"Tim Patrick" <in*****@invali d.com.invalidwr ote in message
news:e3******** *************** **@newsgroups.c omcast.net...

>Gee, this doesn't sound like a technology issue.

SQL Server does run as a service, not as an application like Access, or
as an extension of your own program like OLE DB and the like. SQL Server
Express does have a mode that lets you access an MDF file (similar to an
MDB file) directly instead of through the normal server-based methods,
but I don't know if that method would support multiple users. I've never
used that file-based method, and I think it only applies to the Express
version of the product.

VB2005 continues to support Access just fine, so you're free to continue
with that data source.

-----
Tim Patrick - www.timaki.com
Start-to-Finish Visual Basic 2005

>>Thanks for the prompt reply, but I really do mean that there can be no
server. Using someone elses workstation is not an option either.
Central data storage and individual database engines are mandated.
There is a very large amount of paranoia in this grey suited
organisatio n.

[RobinS]

My impression from the original post was that he had a VB6
desktop app with an Access back-end that he wanted to *rewrite*
in VB.Net, and he wanted to know what we thought he should use
for the database back-end.

It has to be something he can take on his laptop, and the
database must reside on the network server, but the server
can't "run" database server software, like SQLServer.

Are you saying that he should get his company to buy a server and
put SQLServer on it? I thought he said in a subsequent post
that that absolutely was not an option.

So his other choices that I see are Access, or SQLServer Express.
I don't see what's wrong with using Access as the back-end. I'm
assuming they would upgrade it to the most current version, not
use Access97.

Please enlighten me on my misdirection, I'm always willing to
learn.

Robin S.
----------------------------------
"Cor Ligthert [MVP]" <no************ @planet.nlwrote in message
news:eu******** ******@TK2MSFTN GP02.phx.gbl...

RobinS and Patrick,

Do you think that it is helpful to show people a wrong way of use of
tools.

kavsaks organisation is obvious afraid that he build applications in his
organisation and now we are helping to brake those rules with all kind of
bad advices.

He just need to get his application running on his central organisation
server. If not, then the organisation does not need his application.

Just my idea maybe not so well written but I hope you understand what I
want to say. If not I will repeat it.

Cor

"RobinS" <Ro****@NoSpam. yah.noneschreef in bericht
news:kL******** *************** *******@comcast .com...

>You *could* put a SQLServer database out there and use it.
This is from a post by David Browne back in mid-November; he said
you could use SQLServer express for multiple users. These are the
restrictions .

-----
SQL Server Express is well suited to small workgroup environments.
It has no connection limit or workload governer. Rather it is physically
limited to 1CPU, 1GB of RAM and 4GB per database. By default the
installer
doesn't enable remote connections to the database, but that's just to be
"secure by default". You can enable remote connections after the install
and you're good to go.
-----

However, I have to admit, I'd probably use Access, because it's so easy
to manage (assuming the database isn't huge).

Robin S.
-----------------------------

"Tim Patrick" <in*****@invali d.com.invalidwr ote in message
news:e3******* *************** ***@newsgroups. comcast.net...

>>Gee, this doesn't sound like a technology issue.

SQL Server does run as a service, not as an application like Access, or
as an extension of your own program like OLE DB and the like. SQL Server
Express does have a mode that lets you access an MDF file (similar to an
MDB file) directly instead of through the normal server-based methods,
but I don't know if that method would support multiple users. I've never
used that file-based method, and I think it only applies to the Express
version of the product.

VB2005 continues to support Access just fine, so you're free to continue
with that data source.

-----
Tim Patrick - www.timaki.com
Start-to-Finish Visual Basic 2005

Thanks for the prompt reply, but I really do mean that there can be no
server. Using someone elses workstation is not an option either.
Central data storage and individual database engines are mandated.
There is a very large amount of paranoia in this grey suited
organisation .

[Tim Patrick]

I think you read the postings incorrectly. He said that he can NOT let the
database run on the central server. Also, my advice included a continued
use of the Access database with just an updated front end in VB2005. Without
knowing the full specifics of his situation, all we can do is offer general
advice and options. It is up to him to make the right choice.

-----
Tim Patrick - www.timaki.com
Start-to-Finish Visual Basic 2005

RobinS and Patrick,

Do you think that it is helpful to show people a wrong way of use of
tools.

kavsaks organisation is obvious afraid that he build applications in
his organisation and now we are helping to brake those rules with all
kind of bad advices.

He just need to get his application running on his central
organisation server. If not, then the organisation does not need his
application.

Just my idea maybe not so well written but I hope you understand what
I want to say. If not I will repeat it.

Cor

"RobinS" <Ro****@NoSpam. yah.noneschreef in bericht
news:kL******** *************** *******@comcast .com...

>You *could* put a SQLServer database out there and use it.
This is from a post by David Browne back in mid-November; he said
you could use SQLServer express for multiple users. These are the
restrictions .
-----
SQL Server Express is well suited to small workgroup environments.
It has no connection limit or workload governer. Rather it is
physically
limited to 1CPU, 1GB of RAM and 4GB per database. By default the
installer
doesn't enable remote connections to the database, but that's just to
be
"secure by default". You can enable remote connections after the
install
and you're good to go.
-----
However, I have to admit, I'd probably use Access, because it's so
easy to manage (assuming the database isn't huge).

Robin S.
-----------------------------
"Tim Patrick" <in*****@invali d.com.invalidwr ote in message
news:e3******* *************** ***@newsgroups. comcast.net...

>>Gee, this doesn't sound like a technology issue.

SQL Server does run as a service, not as an application like Access,
or as an extension of your own program like OLE DB and the like. SQL
Server Express does have a mode that lets you access an MDF file
(similar to an MDB file) directly instead of through the normal
server-based methods, but I don't know if that method would support
multiple users. I've never used that file-based method, and I think
it only applies to the Express version of the product.

VB2005 continues to support Access just fine, so you're free to
continue with that data source.

-----
Tim Patrick - www.timaki.com
Start-to-Finish Visual Basic 2005
Thanks for the prompt reply, but I really do mean that there can be
no server. Using someone elses workstation is not an option either.
Central data storage and individual database engines are mandated.
There is a very large amount of paranoia in this grey suited
organisation .