Steve Crossman observed in this thread:

>All well and good, maybe USR ScanFolder should be rewritten.
>
>such is always the case, with me being behind the times using legacy 
>/ deprecated code.
>I spent three years rewriting the application for OS X, not paying 
>attention to the future. Just getting something to work.
>Sometimes I wish I would have spent that time learning xCode and 
>Objective C. But there would be nothing to sell.
>
>However, now that the program is working, selling, it can be 
>replaced with more modern plumbing as time permits.
>A lot of time is now spent selling, documenting and supporting 
>several hundred brand new customers.


Steve,

You're the one making money from your code and that trumps anything I 
have to say. I'm strictly a hobbyist while you have a viable 
commercial product on the market.

However, perhaps what I'm suggesting here will help point you in the 
right direction as we soon begin heading down the Intel road. If, 
sometime in the future, your product begins sagging from legacy code, 
at least you will have some ideas as to where to go.

 From a marketing standpoint, one thing about the switch to Intel is 
that it will provide commercial developers with an opportunity to 
release new "Macintel" versions of their existing software with the 
accompanying revenue boost.

If you have several hundred brand new customers, you have your hands 
full. It strikes me that if your code eventually incorporates "modern 
plumbing" perhaps support would be easier, i.e., no more broken code 
when a user uses a long file name, etc.

The nice thing is that if USR ScanFolder is rewritten, its use would 
be relatively transparent.

I wish you the best success and am glad to see your experienced input here.

Ken