| .NET DotNet Forum Index » General Discussion » vb.net design question on version updates... |
|
Page 1 of 1 |
|
| Author |
Message |
| Simon Whale... |
 Posted: Thu Oct 29, 2009 8:20 am |
|
|
|
Guest
|
Hi,
need some design advise. Looking at converting an Access Project into
vb.net but the project undergoes some regular enhancements according to the
business requirements.
Using Visual Studio 2005 what would be the best method to upgrade 40 users
on a version rollout? or would a 3rd party product be better?
Many thanks
Simon Whale |
|
|
| Back to top |
|
|
|
| Scott M.... |
| Posted: Thu Oct 29, 2009 9:08 am |
|
|
|
Guest
|
"Simon Whale" <simon at (no spam) nospam.com> wrote in message
news:Opp54KKWKHA.4780 at (no spam) TK2MSFTNGP05.phx.gbl...
Quote: Hi,
need some design advise. Looking at converting an Access Project into
vb.net but the project undergoes some regular enhancements according to
the business requirements.
Using Visual Studio 2005 what would be the best method to upgrade 40 users
on a version rollout? or would a 3rd party product be better?
Many thanks
Simon Whale
Is it possible to make this an ASP.NET web application and upgrade to SQL
Server? If so, you'd solve your 40 user issue and you'd be able to make
updates as necessary.
-Scott |
|
|
| Back to top |
|
|
|
| Simon Whale... |
| Posted: Thu Oct 29, 2009 9:14 am |
|
|
|
Guest
|
Sadly no as its an insurance underwriting system they dont want to take that
avenue on so it will be a vb.net front end and sql server 2005 back end.
"Scott M." <s-mar at (no spam) nospam.nospam> wrote in message
news:%23%23FqqlKWKHA.844 at (no spam) TK2MSFTNGP05.phx.gbl...
Quote:
"Simon Whale" <simon at (no spam) nospam.com> wrote in message
news:Opp54KKWKHA.4780 at (no spam) TK2MSFTNGP05.phx.gbl...
Hi,
need some design advise. Looking at converting an Access Project into
vb.net but the project undergoes some regular enhancements according to
the business requirements.
Using Visual Studio 2005 what would be the best method to upgrade 40
users on a version rollout? or would a 3rd party product be better?
Many thanks
Simon Whale
Is it possible to make this an ASP.NET web application and upgrade to SQL
Server? If so, you'd solve your 40 user issue and you'd be able to make
updates as necessary.
-Scott
|
|
|
| Back to top |
|
|
|
| Scott M.... |
| Posted: Thu Oct 29, 2009 9:56 am |
|
|
|
Guest
|
"Simon Whale" <simon at (no spam) nospam.com> wrote in message
news:Og7dCpKWKHA.4004 at (no spam) TK2MSFTNGP05.phx.gbl...
Quote: Sadly no as its an insurance underwriting system they dont want to take
that avenue on so it will be a vb.net front end and sql server 2005 back
end.
It can still be a VB .NET front end and SQL back end. ASP .NET just means
that it will use a web-based interface. It can also be an intranet
applicaiton, so that it is secured and only available internally.
Either way, you are going to have to rewrite most of the code since you
won't be using Acess or Access column types or the Access object model or
VBA anymore.
-Scott |
|
|
| Back to top |
|
|
|
| Simon Whale... |
| Posted: Thu Oct 29, 2009 10:11 am |
|
|
|
Guest
|
the rewrite isn't the problem as i have mainly an .net background rather
than access. i meant by vb.net front end that it wasn't to be intrannet /
extrannet based sorry. hence i was after finding out how best to update the
clients for each update after the initial roll out
Simon
"Scott M." <s-mar at (no spam) nospam.nospam> wrote in message
news:eGNeZALWKHA.3720 at (no spam) TK2MSFTNGP04.phx.gbl...
Quote:
"Simon Whale" <simon at (no spam) nospam.com> wrote in message
news:Og7dCpKWKHA.4004 at (no spam) TK2MSFTNGP05.phx.gbl...
Sadly no as its an insurance underwriting system they dont want to take
that avenue on so it will be a vb.net front end and sql server 2005 back
end.
It can still be a VB .NET front end and SQL back end. ASP .NET just means
that it will use a web-based interface. It can also be an intranet
applicaiton, so that it is secured and only available internally.
Either way, you are going to have to rewrite most of the code since you
won't be using Acess or Access column types or the Access object model or
VBA anymore.
-Scott
|
|
|
| Back to top |
|
|
|
| Scott M.... |
| Posted: Thu Oct 29, 2009 10:33 am |
|
|
|
Guest
|
Well, you have several choices depending on whether these updates will be
mandatory or not.
You could build a polling mechanish into the application that fires upon
startup and uses the network to determine if an update is available and if
so initiate a download of the new assembly, which can take the place of the
orginial.
-Scott
"Simon Whale" <simon at (no spam) nospam.com> wrote in message
news:ucn9nILWKHA.4484 at (no spam) TK2MSFTNGP02.phx.gbl...
Quote: the rewrite isn't the problem as i have mainly an .net background rather
than access. i meant by vb.net front end that it wasn't to be intrannet /
extrannet based sorry. hence i was after finding out how best to update
the clients for each update after the initial roll out
Simon
"Scott M." <s-mar at (no spam) nospam.nospam> wrote in message
news:eGNeZALWKHA.3720 at (no spam) TK2MSFTNGP04.phx.gbl...
"Simon Whale" <simon at (no spam) nospam.com> wrote in message
news:Og7dCpKWKHA.4004 at (no spam) TK2MSFTNGP05.phx.gbl...
Sadly no as its an insurance underwriting system they dont want to take
that avenue on so it will be a vb.net front end and sql server 2005 back
end.
It can still be a VB .NET front end and SQL back end. ASP .NET just
means that it will use a web-based interface. It can also be an intranet
applicaiton, so that it is secured and only available internally.
Either way, you are going to have to rewrite most of the code since you
won't be using Acess or Access column types or the Access object model or
VBA anymore.
-Scott
|
|
|
| Back to top |
|
|
|
|
