Having enough data
-
Part of my job is to write stuff in MVC, c#, Sql, etc.. and replace our outdated systems. Doing this requires supporting the older legacy stuff until I can replace it. I'm currently writing a program that is very important to our company. The task I have now is to get some data out of this system and move it over to a database (in access). I can't skip this database (yet) because so much stuff works off of it. No big deal, the goal is to get rid of it, but for now just xfer some data so everything can function as per normal. 62 columns. The "main" table in this database has 62 columns. Lets not get started on data types, misused fields, etc. So I figured I'd just power through it. Nothing to do, it has to be done. Well, then I get a field to small error. Now I have to debug it. So terrible structure aside, the "control" copy of this database (we have a new instance per client) has a definition for said field that is unstable. It's one that needs to be changed per use to fit the data that's being inserted. This isn't documented anywhere. I'll be glad when I get this finished so I can move on.
Elephant elephant elephant, sunshine sunshine sunshine
-
Part of my job is to write stuff in MVC, c#, Sql, etc.. and replace our outdated systems. Doing this requires supporting the older legacy stuff until I can replace it. I'm currently writing a program that is very important to our company. The task I have now is to get some data out of this system and move it over to a database (in access). I can't skip this database (yet) because so much stuff works off of it. No big deal, the goal is to get rid of it, but for now just xfer some data so everything can function as per normal. 62 columns. The "main" table in this database has 62 columns. Lets not get started on data types, misused fields, etc. So I figured I'd just power through it. Nothing to do, it has to be done. Well, then I get a field to small error. Now I have to debug it. So terrible structure aside, the "control" copy of this database (we have a new instance per client) has a definition for said field that is unstable. It's one that needs to be changed per use to fit the data that's being inserted. This isn't documented anywhere. I'll be glad when I get this finished so I can move on.
Elephant elephant elephant, sunshine sunshine sunshine
:omg: First I've heard of that. Should I send some tequila over?
You'll never get very far if all you do is follow instructions.