VLF-WIN Error in deployed version

[atostaine]

We have been deploying our app for years. We did another deployment yesterday and now the users are seeing this error when running one of our commands. This customer doesn't use any filters, all of the commands are business object commands. This is the previous version of VLF, not VLF-ONE

error.png (19.64 KiB) Viewed 7107 times

The app works in the development environment on multiple PC's. No EPC's or hotfixes were done recently. Is there any chance the error is because of something we did wrong?

Also submitted to Support incident# 110513. Hopefully someone there knows what the deal is.

[atostaine]

Turns out that if I eliminate this tree from the RP it doesn't crash the VLF:

Define_Com Class(#PRIM_TREE<#LT_OAINQ>) Name(#Tree_1) Displayposition(3) Height(391) Left(0) Parent(#Sheet_ord) Tabposition(3) Width(105)

This is my component #LT_OAINQ that I've stripped to nothing.

Function Options(*DIRECT)
Begin_Com Role(*EXTENDS #PRIM_PANL *implements #Prim_Tree.iTreeDesign *ListFields #ListFields) Displayposition(1) Height(40) Left(0) Tabposition(1) Top(0) Width(276)

* Fields mapped in when the entry is added to the Tree
Group_By Name(#ListFields) Fields(#std_Desc)

End_Com

[dannyoorburg]

Hi Art,

I'm not sure how you got into this situation, but the thing to check is if

x_win95/x_lansa/execute/lpvo.bnd

actually contains this entry

Code: Select all

List.Filter=Filter

(it's probably the last entry in that file)


If it does, the next thing to check is whether or not

x_win95/x_lansa/execute/lpvo.BNB

has been rebuild after your deployment (this is a binary version of the lpvo.bnd file that's created on first use to speed up lookups)

If it hasn't, you can just delete (or rename) it and it will be rebuild when you next run the program, after which it should contain the List.Filter string.


Cheers,
Danny

[atostaine]

Thanks. Mad I can’t get into that system tonight to try this.

[atostaine]

That worked! Thanks.

Art