|
 |  |  |  |  |  |  |
| Welcome to Windows Vista Forums. Our forum is dedicated to helping you find solutions with any problems, errors or issues you are experiencing with Windows Vista. The Vista forum also covers news and updates and has an extensive Windows Vista tutorial section that covers a wide range of tips and tricks. |
| |||||||
 |
| |
4 Weeks Ago
| #1 (permalink) |
| | vb.net design question on version updates 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 |
My System Specs |
|
4 Weeks Ago
| #2 (permalink) |
| | Re: vb.net design question on version updates "Simon Whale" <simon@newsgroup> wrote in message news:Opp54KKWKHA.4780@newsgroup 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 |
| My System Specs |
|
4 Weeks Ago
| #3 (permalink) |
| | Re: vb.net design question on version updates 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@newsgroup> wrote in message news:%23%23FqqlKWKHA.844@newsgroup Quote: > > "Simon Whale" <simon@newsgroup> wrote in message > news:Opp54KKWKHA.4780@newsgroup 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 > |
| My System Specs |
|
4 Weeks Ago
| #4 (permalink) |
| | Re: vb.net design question on version updates "Simon Whale" <simon@newsgroup> wrote in message news:Og7dCpKWKHA.4004@newsgroup 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. 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 |
| My System Specs |
|
4 Weeks Ago
| #5 (permalink) |
| | Re: vb.net design question on version updates 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@newsgroup> wrote in message news:eGNeZALWKHA.3720@newsgroup Quote: > > "Simon Whale" <simon@newsgroup> wrote in message > news:Og7dCpKWKHA.4004@newsgroup 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 > |
| My System Specs |
|
4 Weeks Ago
| #6 (permalink) |
| | Re: vb.net design question on version updates 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@newsgroup> wrote in message news:ucn9nILWKHA.4484@newsgroup 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@newsgroup> wrote in message > news:eGNeZALWKHA.3720@newsgroup Quote: >> >> "Simon Whale" <simon@newsgroup> wrote in message >> news:Og7dCpKWKHA.4004@newsgroup 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 >> > |
| My System Specs |
|
| Thread Tools | |
| |
Similar Threads | ||||
| Thread | Forum | |||
| OO design question | .NET General | |||
| Question on design involving some Generics | .NET General | |||
| RTF Question: Is this a bug or by design? | Vista General | |||
