What causes an Error 78 and/or sometimes "phantom" records in a browse?

[CarlBarnes]

@Mark_Sarson

All our KEYS are < 1024 characters in size, so in SQL’s case it seems the problem is not just down to cutting back KEY size

I think its not the one Primary File’s Key Position Size, but that the Browse uses Position(View) that includes position info for the Secondary Joined Files. I pasted info in the below topic. Also 1 post lower down a quick idea to throw the LEN(Position(View)) in the Browse to see it.

WindowManager.Update calling BrowseClass.UpdateViewRecord - RC = ErrorCode() - Error 78 Invalid Number of Parameters

Getting the Longest Length from only the Primary file does NOT look like the fix for a Browse. The Browse uses ViewPosition = POSITION(View) and not just POSITION(Primary). According to the Help on POSITION(View) the Position String includes all Secondary File Keys i.e. Join(, Secondary File Key). So you need to walk the View files and add the length of those keys. The help hints that the Position is driver specific (aka “underlying file system”) it’s not documented. I wonder if the Position …