hence, if the original system is not documented, then i would strongly suggest that a er diagram of the tables be created. not only does this aid in the conversion process, it allows one to "see" the big picture. this "picture" will save a large amount of time in both the conversion process, and design of the new system. when my er diagram was done, i pasted it on wall in view at all times. it was worth it heaps of gold.  appendix #1 has an actual example of mine.


so, given the above, i will make my first trap warning about converting software from pick to ms-access/sql


conversion got ya #1:

pick allows you more freedom to make mistakes from a table design point of view. sql does not. you need more effort and skill to get the sql table design correct. so, make sure your data structures (tables) are of a good design.



code and business rules:

it is interesting how i just ranted about how you must get the table design correct. in fact, i will just assume that a good job is going to be done in the table area. we are wasting time if we cannot assume the table design is good. ok, so if the table design is good, then it not a problem anymore is it?

so, then ?.just what is the problem we are left to deal with ?

where the conversion from pick to vb/sql will kill you is in the business rules.

i am going to say this again:

conversion got ya #2:

where the conversion from pick to vb/sql will kill you is in the business rules.


while pick may be really great from a data point of view, it shines when it comes to business rules. i'll define business rules in my context, since we hear the term all the time.


business rules  =  code that manipulates >far too many of the new "mainstream" database people seem to think that a application is a bunch of tables, and screens to enter data. far from it. if this was the case then we would not need programmers anymore. we would only need people to build data entry screens and tables. this simple "table" approach is why pick to sql applications fail. in fact it is why a lot of conversion projects fail. one just has to read the disaster enclosed in appendix 4 to get an idea of how wrong things can go. to be fair, the disaster outlined in this appendix 4 is due to the people involved, however the ability of the pick system must also be considered here.