New installs may be killing our LANS

I'm really grasping at straws here. I have an update and on a couple of
networks (so far) our program cannot open the data files, create, or
write on the server. The server is just a windows 10 machine, all worked
fine before they did the update.

The big thing I added to the install was registering an ocx.

I can run the program on each machine just fine, but when I use the
mapped drive to the server in the start in (in the shortcut), it gets an
error opening the first file. If I just go directly to the server from
the workstation it gets the same error. I can see all of the files, but
cannot run across the lan.

Again, the only thing I did to the install was install this ocx and
register it.
\
thanks,

--
Ray Rippey
VMT Software

Maybe you should use RegFree.

Jeff Slarve
www.jssoftware.com


Bits and Bytes are Dy-No-Myte

Yes, I think I should. Seems more complex but safer. I found the issue
was a permissions issue with inheritance thanks to a network tech guy at
their company. Now at least I know what to do. Just need to figure if
registering this OCX would be causing the permissions issue to show up,
or it's something else I may have done in the install.

Ray Rippey
VMT Software

Registering a remote OCX on a workstation seems more complex to me.

Jeff Slarve
www.jssoftware.com


Bits and Bytes are Dy-No-Myte

I just did it with SetupBuilder. I install to each machine anyway.

Ray Rippey
VMT Software