Reworking somebody else's code
-
...is there anything more frustrating in a developer's life? For the past week or so I've been modifying a third party's Excel VBA to run against SQL Server rather than Access and constantly find myself asking "why the #### have you done this?!" It's a good thing the author isn't in the same office else I may have ended up swinging at him. :mad:
-
...is there anything more frustrating in a developer's life? For the past week or so I've been modifying a third party's Excel VBA to run against SQL Server rather than Access and constantly find myself asking "why the #### have you done this?!" It's a good thing the author isn't in the same office else I may have ended up swinging at him. :mad:
-
I feel your pain, I'm currently trying to rework somebodies else's VB code - and they didn't believe in comments. :mad:
Better no comments than wrong comments... (And yes, I do believe in comments)
This message is manufactured from fully recyclable noughts and ones. To recycle this message, please separate into two tidy piles, and take them to your nearest local recycling centre. Please note that in some areas noughts are always replaced with zeros by law, and many facilities cannot recycle zeroes - in this case, please bury them in your back garden and water frequently.
-
I feel your pain, I'm currently trying to rework somebodies else's VB code - and they didn't believe in comments. :mad:
-
This one's just plain mad. Quick pseudocode: Sub DeleteRecord 1) Copy entire database table into Variant array 2) DROP TABLE 3) CREATE TABLE 4) Write everything back apart from the record we don't need
Well... It works.. So what's your problem with that way :laugh:
-
This one's just plain mad. Quick pseudocode: Sub DeleteRecord 1) Copy entire database table into Variant array 2) DROP TABLE 3) CREATE TABLE 4) Write everything back apart from the record we don't need
Classic. What happens when a record is queried? Is the entire database backed up, deleted, recreated without the unwanted records and then rolled back to what it was pre-query?
If there is one thing more dangerous than getting between a bear and her cubs it's getting between my wife and her chocolate.
-
This one's just plain mad. Quick pseudocode: Sub DeleteRecord 1) Copy entire database table into Variant array 2) DROP TABLE 3) CREATE TABLE 4) Write everything back apart from the record we don't need
Can you not re-badge this is "Database Memory Leak Detector" and "Hard Drive Stress Tester" feature?
-
Classic. What happens when a record is queried? Is the entire database backed up, deleted, recreated without the unwanted records and then rolled back to what it was pre-query?
If there is one thing more dangerous than getting between a bear and her cubs it's getting between my wife and her chocolate.
-
No, in order to do that it also copies the entire table into a worksheet, then does a lookup from there! (I can't be bothered to even look into what that's used for.)
Perhaps the developer was playing it safe. You can never be too careful. :laugh:
If there is one thing more dangerous than getting between a bear and her cubs it's getting between my wife and her chocolate.
-
...is there anything more frustrating in a developer's life? For the past week or so I've been modifying a third party's Excel VBA to run against SQL Server rather than Access and constantly find myself asking "why the #### have you done this?!" It's a good thing the author isn't in the same office else I may have ended up swinging at him. :mad:
Reworking your own code, half of your brain is busy making excuses.
-
Reworking your own code, half of your brain is busy making excuses.
