Is this a good idea or not?

I am still fairly new at programming and learning. I have some VB.Net and ASP.Net under my belt but not enough to feel comfortable telling the bosses that what they want to do is good or bad.

Currently we have a website, works great, asp/html front and Access back end. The concerned part of the website is that it tracks our customers when they go to the product update pages. Stores this in a database table. We have an in house support log that we use to track customers calls and other info. This also uses an Access database. Once a week I import data from the web database to the in house support log database.

The bosses want to make an asp.net site that links to a SQL database (yeah). They want to redo the in house support app, vb6 to vb.net however they want it to remain in house and connect to a SQL database (yeah). They want the SQL server to remain in house and have the web app communicate with it. The web site will be hosted somewhere else.

Is this a good or bad idea?

Is this a good idea or not?

So you just want an asp page in order to view the stuff from the database?

Is this a good idea or not?

anything that moves it out of Access is a good thing! personally it will be much cheaper ( and can be better secured) by hosting the website in house. it%26#039;s not that complicated to do. converting the vb6 is a good idea (but i%26#039;d choose something other than VB....but i understand it%26#039;s easier to convert than rewrite from scratch)

Other Replys:sounds ok.........

Other Replys:You want to give world access to your in-house database? (You%26#039;ll have to, to let the outside web site access it, even if you do all sorts of passwording.)

Tell the bosses to just accept the judgment now, and avoid the whole lawsuit, when their customer information appears in the public domain, and the customers institute a class-action suit.

*B*A*D* idea.

Web site internally - better idea. (All it costs is a box and a port on the switch - the software to run on it is free. )