Is this going to be a good idea?

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?

I am more of a mind to develope the website with a webservice that the in house support log can go to, to get the data it needs from the web site. The information that is passed is not sensitive and is only relevant to our application.

Is this a better idea? or is there something else that I don't know about?