even created macro from Sage 300 to OE screen and then outside of sage edited/run it and same thing   OE0520 and OE0500 views do not create anymore.

Noticed someone installed Office 2016 Home and Bus 16.0.12228.20100 32bit - build 1911 just before this showed up. I know in the past this has messed up AVB but is just 2 views - that is weird.

Any info or guess would be appreciated,

Did REGACC,  reinstalled VBA.msi, 2018 PU1 (that is what they use), created 2nd session in new macro and still failure on these 2 views; deleted all EXD and BOX files on server.

Does the macro still work in  another environment like your server?

yes on my own station it works; they key part is record a macro in Sage 300 going into the OE screen and change a simple field.  if you run the macro then under Sage 300 it creates the view; if you edit the macro outside of Sage 300 the view does not create and only the header and detail1 does not work, other detail views work.

I am going through users and Server I.T. people to find out who installed Office ( and maybe other stuff) on Dec 12 and why; so far no one confesses. Does not sound like a normal Microsoft messing with VBA - messing only 2 views of 12 - strange

Sounds like definitely an environment issue.  All of my macros I've done always run inside of Sage 300 so I've not faced this issue.

Please let us know what you find.

Dana

fixed now

3rd party web software  had attached to OE and when I went to create OEHDR view it tried to make their views also; but their software is web based and doesn't even need to attach to standard OE screen.

modified CSAPP table to change their abbreviation on the OE lines to something like XX that is not used and then OE cannot communicate with this software

found this out by using RVSPY when macro run inside Sage and outside Sage just on create command for OEHDR view.