Author Topic: Command-s  (Read 259 times)

0 Members and 1 Guest are viewing this topic.

hobleglobsquishyworms

  • Swamp Rat
  • Posts: 779
  • .net stuff
Command-s
« on: August 08, 2019, 02:31:21 PM »
Have a ton of routines that recently started getting the command-s error, though we've been on 2018 for a considerable amount of time where the routines had been working.

Anyone know what triggers this?

Coder

  • Swamp Rat
  • Posts: 771
Re: Command-s
« Reply #1 on: August 08, 2019, 02:37:24 PM »
Replace with vl-cmdf function.

hobleglobsquishyworms

  • Swamp Rat
  • Posts: 779
  • .net stuff
Re: Command-s
« Reply #2 on: August 08, 2019, 04:03:09 PM »
Replace with vl-cmdf function.

Thanks.  I've seen a few other solutions also, but trying to understand what actually causes it to break. The routines were fine last week running on 2018. This week, they aren't.  As far as I'm aware there hasn't been updates. 

Guess a clearer question would be should they have kept working as they have and that somehow we were lucky until now... 

I'm thinking it might be a windows thing tied to it (registry or something) but really don't know anything about it specifically
« Last Edit: August 08, 2019, 05:35:11 PM by quaziconscience »