>>>Terry - I had mentioned InnoSetup to you some time ago - what happened ? you decide not to use it after all ? o-k][d-o-k-i-e
>>
>>I know - I know - I know - life was so simple when all I had to do was:
>>
>>@ nn,nn get m.myvariable pict '9999' valid required chekitout()
>>
>>ISE is a second career. Volunteerism capitalism. Who else can I pay to report bugs to?
>
>Terry - before we hihack this thread about INNOSETUP completely -
>you paid nothing for ISE - it came with VFP 7 and 8.
>can we float back to David's question ?
>What do you like about INNOSETUP and why ?
>mondo regards [Bill]

I've heard of it - have not used it. So much VFP stuff to keep up with - to little time for evaluations. IF someone would share a case, ISE vs Inno, and cited that Inno installed on all XP desktops without issue, while ISE on hit on about 70% - I would make the switch.

It seems with XP it's [too] easy for novice system administrators to over tweak desktop security. Talk "group policies" an their eyes roll. Even these same admins will admit that they are spending an inordinate amount of time with "Regi-mon" to get other vendors stuff to run. (MS - Why?) Set that aside, we still have ISE issues. What's DIskImage.Bak?:-). Maybe clunking with AddResource to add fonts would be less risky than ISE's resource "manager"? Why is edit access to forms with ocx controls locked out until a system re-boot?

Can you tell me that Inno will always install and not make me feel like [if] I will be purchasing the full version to [just] report bugs? I don't want to be an InstallShield (or Inno) expert. I just want to be a dumb user and build my project setup without hiccups!

Microsoft needs to address this stuff in simple, clear and precise terms. If not just for me, then for all those green Admins out there driving "Regi-mon" just to get vendor software to work. OLEDB may be the way of GE, but mom and pop are ejoying the heck out of drive mapped data!

Am I back on topic?