I have Visual Basic 6 Pro, Service Pack 4 on an old, spare PC loaded with Windows XP Pro which I use to run some older programmes not compatible with Win 10. It's been working away happily for around 6 years with all my other legacy programmes but I haven’t used VB on it since February 2016. I recently needed to update some schematic drawings but I now find that although I can still open the files, the software is in "view only" mode meaning I can no longer create, change or save files.
It keeps asking me to load visio.msi from my installation media but neither my CD's version of VB6 or service pack 4 has this file. I know MS no longer support XP but did one of the last XP auto updates do something to my installed OS as a "parting gift" that would restrict it to read only mode? If so why & is there a way around it? anyone know what’s going on?
Would re-installing the XP Pro, software I have without the later MS updates before they stopped support restore the status-quo? I use VB so little now & don't want to go to the expense of buying the latest Visio package!
It keeps asking me to load visio.msi from my installation media but neither my CD's version of VB6 or service pack 4 has this file. I know MS no longer support XP but did one of the last XP auto updates do something to my installed OS as a "parting gift" that would restrict it to read only mode? If so why & is there a way around it? anyone know what’s going on?
Would re-installing the XP Pro, software I have without the later MS updates before they stopped support restore the status-quo? I use VB so little now & don't want to go to the expense of buying the latest Visio package!