How would you do that?
-
hi, for the next release my company wants me to do something which changes a lot in the existing object model of the product i am working on. That would take about 4 weeks to do that cleanly. Don't ask why it takes that long, let's say it is "legacy" code. Old VB objectmodel/ UIs with a lot of things you won't see. Therefore the idea came up to do the something quick and dirty: Just change the information in the database and restart the application via a sqlscript. As all the other solutions which must be done in a very short timeframe also this one shall only stay until the functionality is available in the objectmodel. (I wonder if this solution will last for ever when it is available once :-) ) How to do that: 1. Create a stored procedure a) which can be used by the consultants and can be taken away when the objectmodel is capable of the feature b) and create a (very small) user interface and throw both away when the objectmodel is capable of the feature. (and don't tell the consultants that this function is available at all) 2. create a batch file which can be called with parameters to do the job All possibilities arent good solutions to me..but anyway it has to be done. At least I prefer 1.b as it seems to be the only solution which that the user doesn't have to switch to another application. On the other hand I guess if this works nobody will invest the time do to the clean solution as this works. What do you think? da5id
-
hi, for the next release my company wants me to do something which changes a lot in the existing object model of the product i am working on. That would take about 4 weeks to do that cleanly. Don't ask why it takes that long, let's say it is "legacy" code. Old VB objectmodel/ UIs with a lot of things you won't see. Therefore the idea came up to do the something quick and dirty: Just change the information in the database and restart the application via a sqlscript. As all the other solutions which must be done in a very short timeframe also this one shall only stay until the functionality is available in the objectmodel. (I wonder if this solution will last for ever when it is available once :-) ) How to do that: 1. Create a stored procedure a) which can be used by the consultants and can be taken away when the objectmodel is capable of the feature b) and create a (very small) user interface and throw both away when the objectmodel is capable of the feature. (and don't tell the consultants that this function is available at all) 2. create a batch file which can be called with parameters to do the job All possibilities arent good solutions to me..but anyway it has to be done. At least I prefer 1.b as it seems to be the only solution which that the user doesn't have to switch to another application. On the other hand I guess if this works nobody will invest the time do to the clean solution as this works. What do you think? da5id
-
I would try the SQL/ Database forum.
Visit http://www.notreadytogiveup.com/[^] and do something special today.
yes, obviously. :-) The discussion of the procedure of doing something (senseless) like this was also something I wanted to know what people think.
-
hi, for the next release my company wants me to do something which changes a lot in the existing object model of the product i am working on. That would take about 4 weeks to do that cleanly. Don't ask why it takes that long, let's say it is "legacy" code. Old VB objectmodel/ UIs with a lot of things you won't see. Therefore the idea came up to do the something quick and dirty: Just change the information in the database and restart the application via a sqlscript. As all the other solutions which must be done in a very short timeframe also this one shall only stay until the functionality is available in the objectmodel. (I wonder if this solution will last for ever when it is available once :-) ) How to do that: 1. Create a stored procedure a) which can be used by the consultants and can be taken away when the objectmodel is capable of the feature b) and create a (very small) user interface and throw both away when the objectmodel is capable of the feature. (and don't tell the consultants that this function is available at all) 2. create a batch file which can be called with parameters to do the job All possibilities arent good solutions to me..but anyway it has to be done. At least I prefer 1.b as it seems to be the only solution which that the user doesn't have to switch to another application. On the other hand I guess if this works nobody will invest the time do to the clean solution as this works. What do you think? da5id
Bad stuff lingers forever. Even if you implement the change correctly later, you will end up maintaining the "quick and dirty" solution forever. The right answer is to do it correctly the first and only time. The 4 week wait will be worth it.
-
Bad stuff lingers forever. Even if you implement the change correctly later, you will end up maintaining the "quick and dirty" solution forever. The right answer is to do it correctly the first and only time. The 4 week wait will be worth it.
yes, that was exactly what I told them. I now agreed to the compromise, that the quick and dirty will be hard bind to the version it is built for. That means that this tool will not work in previous or later versions. If the tool must exist in a later version it must be discussed again. that's sounds reasonable to me.