I really have 2 items.
The commondialog box cancelerror statement.
My app was\in written on a Vista computer.
I have a On error statement in the beginning of the command button
code.
When I set the CommonDialog.cancelerror to TRUE, when selecting the
cancel button it acts like to doesn't even see the error routine, and >immediately gives me the Runtime Error 32775 Cancel Was Pressed and
then exits the program. When i do the same on my Windows 10 computer
it works just like it should. Anyone know what Im doing wrong.
The second item (which if fixed will take care of the first item) is
that my app uses FarPoint controls Input pro and tab pro from a
million years ago. I can not install these controls on my windows 10 >computer. Farpoint is out of business, i believe that
ComponetOne\GrapeCity bought them out but I get the deer in the
headlight look from them.
Anyhow everytime I try to install them on my windows 10 computer I
get a "This Program Can Not Run On This Machine" message.
I tried the different compatability modes - nothing.
I know the controls work fine on windows 10 cause the app has been
installed on these machines and runs just fine. It seems to just be
the installer for the tools that's not working.
Any Idea's
Thanks in Advance
The second item (which if fixed will take care of the first item) is
that my app uses FarPoint controls Input pro and tab pro from a
million years ago. I can not install these controls on my windows 10 computer. Farpoint is out of business, i believe that
ComponetOne\GrapeCity bought them out but I get the deer in the
headlight look from them.
Anyhow everytime I try to install them on my windows 10 computer I
get a "This Program Can Not Run On This Machine" message.
I tried the different compatability modes - nothing.
I know the controls work fine on windows 10 cause the app has been
installed on these machines and runs just fine. It seems to just be
the installer for the tools that's not working.
Any Idea's
Any reason you can't just copy the files and manually register them?
(That's what i did to migrate from XP machine to Win7 Pro machine;
-worked just fine!!)
Any reason you can't just copy the files and manually register them?
(That's what i did to migrate from XP machine to Win7 Pro machine;
-worked just fine!!)
Ah.., not exactly! I wanted to test drive TabPro and without the >ProductCode/SerialNo it only ran on the Win7 machine as a 'trial'
(which long ago expired)<g>
I believe that I still have the product codes\serial numbers.
I always thought that there was some kind of magic in the installer
program.
I'll try the copy and register them myself.
Which files did you copy - just the .ocx's ?
Will the program compile out correctly ?
If this works I'll be one happy camper.
On Fri, 16 Dec 2016 19:28:34 -0500, GS <gs@v.invalid> wrote:
Any reason you can't just copy the files and manually register
them? (That's what i did to migrate from XP machine to Win7 Pro
machine; -worked just fine!!)
Ah.., not exactly! I wanted to test drive TabPro and without the
ProductCode/SerialNo it only ran on the Win7 machine as a 'trial'
(which long ago expired)<g>
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 295 |
Nodes: | 16 (2 / 14) |
Uptime: | 20:49:25 |
Calls: | 6,640 |
Files: | 12,188 |
Messages: | 5,325,292 |