So I finally got my new computer for other machine. Did a fresh new install of PC-DMIS and Datapage +5.2, on windows 10. So a few of us still use the External Command, Listening at the top and End at the bottom. Well if you don't install Datapage 5.0 and install 5.2, this little knickknack don't work. spent all day with Hexagon just to find this out. Now if you put External Command without -END or -E it works which takes a while to record. You have to have Data Importer 5.0 gathering info and Datapage 5.0, and it will still show up in DataPage 5.2. Now it actually seems to work fine on my windows 7 computer, even though I have both Datapages installed, I do use the Data Importer 5.2 gathering the information, results no problem. So I'm kinda guessing this might be a Windows 10 thing. Now Stats update seems to work no problem.
One more thing to add, I'm sure Hexagon will get right on this and fix it
First, Walter in support is rock solid when it comes to Datapage I'd trust him. But typically I don't see any issues with 5.0 or 5.2 in regards to data recording in Windows 10 unless you're doing something like running PC-DMIS as admin which in Win 10 with UAC disabled doesn't really do much except change the user that's running it without actually elevating the process to admin.
First, Walter in support is rock solid when it comes to Datapage I'd trust him. But typically I don't see any issues with 5.0 or 5.2 in regards to data recording in Windows 10 unless you're doing something like running PC-DMIS as admin which in Win 10 with UAC disabled doesn't really do much except change the user that's running it without actually elevating the process to admin.
Oh I didn't feel any doubts of his ability. He even stated that there seemed to be an issue with 5.2 and he was going to submit something, not sure what, but he said there seems to be a problem. He actually saw the popup, he downloaded something, he said reboot it and it should go away. I did all of that and the popup was still there, and as you can see above, recording with no results. Walter and I spent over 2 hours with no progress.
I would have to get my hands on the system to see what's going on but I'm pretty sure I could figure it out. I recall one of the data tools packages not adding or specifying the wrong text file encoding causing SQL to dump all the data, so that's a possibility. How do you process your data files? Do you delete them after you add them to the database or do you handle them to a backup directory? I'd like to take a look at the data file that failed to import into the Database, be nice to see if encoding was the issue or something deeper.
Sp2. I don't have the PC hooked up right now. Had to resort back to my old PC, so it will work. I have IT just reverting back to Windows 7. I think 5 hours of wasted time on this is plenty. I appreciate everything Peter, we're just gonna go back to what works
