Re: VB6 to VB.NET project
What I would do would be this:
1) Leave them using the current version with the current setup, because inventory has to be completed by the end of January. If you start into a total re-write and expect it to be up, running, and stable in one month with just you working on it, this project has to be considerably simpler than you make it sound.
2) Set up SQL Server. If you have a functioning Access DB, you probably have the table structure you need, or close to it, already, so migrating that to SQL Server isn't going to be huge.
3) Start work on the new project against SQL Server while the working version is working against the functioning Access DB.
4) Once the new project is up and tested, migrate the existing Access DB data into SQL Server.
5) Stop using the old program and start using the new one.
Re: VB6 to VB.NET project