Sage 100

v2016.2 Upgrade (from 4.40.8) Upon _accessing_ the v2016 CO UDF Report, I get an error 27, cm_udfmaint_ui.pvc, 399, cm_options.m4t. Prior to that I realized I also get an error upon trying to print the UDF Report in 4.40: error 47, sy_selection.pvc, 240, gl_detailposting.m4t. With much-appreciated assistance from @KennethPhillips at DSD, I was able to print the UDF Report in 4.40 after I temporarily manually reinitialized sy_reportselection.m4t. I then tried the same thing in v2016, but no luck. Help, please.

I received a program update from ACS (Prop Mgmt) for CM_UDFMAINT_UI.PVC. That resolved my error 27 in v2016, but now I'm getting an error 47 upon _printing_ the UDF Report, which is similar to the error I get in 4.40 (diff line #323) - although I am able to access a file/table in v2016 that contains a UDF in order to run the UDF Update, which worked. Still want to resolve this error 47 in v2016. Waiting to hear back from ACS.

Now that we have an error 47 in v2016 that's similar to the error 47 in 4.40, I tried temporarily manually reinitializing the sy_reportselection file in v2016, and that allowed us to run the UDF Report just like 4.40. So it appears there's something in that file causing the issue/error.

How many records are in your table? Err 47 is a substring reference error which usually means a string in a file is too short. If you don't have too many entries, I recommend dumping the whole table to Excel and visually scanning for something that looks weird... good luck

1,095 records. Thanks, @RandyMarion, that's actually what I was gonna try next.

With that many records, as you probably already figured out, recreating all the entries would be quite tedious... I would try to find the culprit. I still think the dump to Excel, since it puts everything in nice, neat columns is the best bet for a visual scan of the data...

Fyi, I pulled the sy_reportselection file into Excel, but nothing's jumping out at me re: any bad/corrupt records. And because the error references the gl_detailposting file, that's what I focused on although I suppose the error could relate to other files as well. I really was hoping there was a way to determine which record(s) is causing the error (e.g., Debug command), but DJ at Sage said there isn't a way.

I'm SOL at this point.