MTSkull
Centurion
I just wanted to thank this forum for all its help.
In July I started to work on an upgrade that would move some of my companies programs from Visual Fox Pro to SQL Server. The first reason; in this area a good inexpensive Fox Pro programmer is very rare, but there are tons of SQL server people out there. The second reason; the parent company wants us to move to .net and SQL server because that is what they use. So in July I spent a solid month working on a .net shell that I could then customize to fit the needs of the project. The project I was originally designing for got scrapped and the .net shell went on the back burner.
The first week of December we got in a new project that we would be taking over from another vendor. They were required to turn over there data to us so we could continue the project. They submitted it to us an SQL server backup file. The specs for the project were way outside anything we had in Fox Pro so I got the nod to connect the .net shell to the SQL data from the other vendor.
Today I had a second meeting with the data entry people for training. The fixes that I took out of this meeting where minor. So I fixed them, compiled and saved it to a folder on the network.
Then I had the IT guy go to all the computers that required the program and Load .net architecture and SQL server Client. I just got back from dropping the first folder into the first computer. The program came right up connected to the server and I could see all the data. I still have a huge list of must fixes and nice to haves, but is real nice to roll out V1 software, and have overall good comments from the people who will be using it.
So this post is for everyone who helped me out here, I could not have done it without this Forum. Thanks Everyone.
MTS
In July I started to work on an upgrade that would move some of my companies programs from Visual Fox Pro to SQL Server. The first reason; in this area a good inexpensive Fox Pro programmer is very rare, but there are tons of SQL server people out there. The second reason; the parent company wants us to move to .net and SQL server because that is what they use. So in July I spent a solid month working on a .net shell that I could then customize to fit the needs of the project. The project I was originally designing for got scrapped and the .net shell went on the back burner.
The first week of December we got in a new project that we would be taking over from another vendor. They were required to turn over there data to us so we could continue the project. They submitted it to us an SQL server backup file. The specs for the project were way outside anything we had in Fox Pro so I got the nod to connect the .net shell to the SQL data from the other vendor.
Today I had a second meeting with the data entry people for training. The fixes that I took out of this meeting where minor. So I fixed them, compiled and saved it to a folder on the network.
Then I had the IT guy go to all the computers that required the program and Load .net architecture and SQL server Client. I just got back from dropping the first folder into the first computer. The program came right up connected to the server and I could see all the data. I still have a huge list of must fixes and nice to haves, but is real nice to roll out V1 software, and have overall good comments from the people who will be using it.
So this post is for everyone who helped me out here, I could not have done it without this Forum. Thanks Everyone.
MTS
It's good to hear a success story among a sea of code