I figured the same...I thought that the code for "everything 7" had already been installed with the Home package and given a Home, or Pro, or Ultimate authorization code, Win7 would act accordingly...turning on and off features. Not so.
After putting in the $77 code, it took about 10 to 15 minutes to download and install quite a bit of stuff. (No idea what or how much as the screen was pretty non-informative as the process progressed.) The process also rebooted twice...good old Windows...just to let me know it was authentic. I did find, also, that sys(3050,1) throws an error on the 64-bit Win7 Pro, but not the 32-bit Home or Pro. That was in the SETMEM.PRG routine that I got from Ed's board years ago. I could be wrong because I didn't spend a lot of time testing, but it didn't appear that sys(3050) did anything at all in any of the versions of Win7. Mike > > On Sat, 05 Mar 2011 17:18 -0600, "Mike Copeland"<[email protected]> > wrote: >> PROBLEM SOLVED >> I think it's pretty obvious: >> There is a system function call being used by the DBI ctGrid (both >> version 3 and 4) OCX file when it is accepting data input for the grid >> combo that Win7 Home Premium does not support well. > I would have thought Home and Pro are code-identical apart from how they > are activated. _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[email protected] ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
