Please confirm if there is any chance to have Sheridan Data Widgets compatible with Windows 7 64-bit.
I had the same problem, finally I found a solution:
- You need XP (or older), install te sheridan product(s) with the CD(s)
- Search for the lisence keys in windows-register (regedit), only the last part is enough
- export all the found keys (in regedit), make sure that you found the key in 2 parts of the register (local_machine\software\.. and class_root\...)
- on win7 copy the ocx files from the sheridan CD (with explorer)
- on win7 execute the .reg files and .... IT WORKS, no demo mode
It cost me a long time surfing on the internet, finally I used my own brains:-)
I hope it works for you
Thank you for taking the time to contact us regarding the status of Sheridan Data Widgets. This is a retired product and is not supported in the Win 7 environment. Please let us know if you have any other questions.
Thanks to Ron for your suggestions.
Hi,I've done another way of installing < Sheridan DevToolKit 2.3 \ AutoRun.exe > the Sheridan Data Widgets 3.12 on the Windows 7 Professional. Make sure to uncheck the 16-Bit control. During the installation it seems to be fine until at the end it could not execute C:\Windows\REGSVR.EXE. I believe related to the Microsoft register server. The error 'The version of this file is not compatible with the version of Windows you're running. Check your computer's system information to see whether you need an x86 (32-bit) or x64(64-bit) version of the program, and then contact the software publisher'.Here are the steps that resolved my issue. 1. Rename the original file > C:\Windows\REGSVR.EXE 2. Copy \Windows\System32\REGSVR32.EXE to \Windows 3. Rename \Windows\REGSVR32.EXE to REGSVR.EXE 4. Re-launch AutoRun.exe 5. Confirm the target location c:program files(x86)\Sheridan\DataWidgetsHope this help. Mark
I work for a major corporation ... we are using Data Widgets 3.12 n an application that works under Windows XP but has a problem running under Windows 7. Our VB6 application has data loaded in the Data Widgets grid (SSDBGrid) and then after you select a Print option from the application menu, the program calls a PrintData method contained in the SSDBGrid control to print the grid contents. In an XP installation, the grid control displays a window that contains a "Printer" button. When you click this, it displays another dialog that allows selecting a printer and then the contents of the grid are sent to the print driver. I'm guessing the functionality of displaying the printer dialogs all happens inside the SSDBGrid control.
In the Windows 7 install, when you call the "PrintData" method, the printer dialog appears but the "Printer" button is not displayed. I'm guessing that the Infragistics control is looking for installed printer drivers in locations in the registry that worked for Win XP, but doesn't find these same registry entries in a Win7 installation. The problem that we're seeing is that the Print dialog appears, but the "Printer" button is hidden. I'm assuming that the drivers aren't found on Win7 where the grid control logic is looking ... therefore it thinks there are no printers so it makes the “Printer” button invisible. In short, the users can’t print the contents of their grid. I hope you can help with this problem.
Can you confirm my assumption and offer any solutions?
I see from the form I'm filling out that the Sheridan Data Widgets is unsupported in Win7. Can you tell me if there is another product that we could upgrade to that replaces the 3.12 Data Widgets product which does run in Win7 ... hopefully with the same grid functionality and interface?
If there is no Win7 compatible product and if we continue to use the XP Data Widgets, do we have any options? If the problem is as I describe, would a solution be to copy the Win7 printer driver to registry locations where Data Widgets software is looking? What have other companies done that have faced this same problem?
And if my assumption is incorrect, and the registry isn't involved, can you tell us what is causing the problem so we can try to determine a solution?
I'm just trying to determine my options in how to troubleshoot this problem. Any help that you can provide would be appreciated.
Union Pacific Railroad
... can you confirm my theory?
I am not sure what was used for the print dialog in the COM controls and it is likely an old MFC print dialog or something like that. As far as using them on Windows 7, the toolset was retired long before Windows 7 was released so you may want to see if the application will work correctly when running in compatibility mode. To do this, create a shortcut for you application and in the shortcut properties go to the compatibility tab and select an older version of Windows where your program ran.
Another alternative that you could look into is running the program on a Windows XP machine and using some remote access technology like Citrix to access it.
Let me know if you have any questions.