Try to specify the column width also, like this

BROWSE FIELDS item1:10, item2:5, item3:15, item4:20 … FONT 'Tahoma',8 NODELETE NOAPPEND NOMENU NOREFRESH WINDOW

>Hi all,
>
>although i posted this problem already some months ago, i'll try it again, because the problem is still there and our customers don't understand it.
>
>We use in our application (vfp6, sp5) the browse-command for building pickup-lists. It works very well, but sometimes it happens, that one column in the browse-window is missed and/or the order of the columns is not correct.
>
>For example:
>BROWSE FIELDS item1, item2, item3, item4… FONT 'Tahoma',8 NODELETE NOAPPEND NOMENU NOREFRESH WINDOW ...
>
>The result in the browse-window is: item1, item4, item3
>Item2 is completely missed.
>
>- We use no RESSOURCE-File (RESOURCE=OFF in CONFIG.FPW)
>- No LAST-Clause in BROWSE
>- No PREFERENCE-Clause in BROWSE
>
>The problem is not solved after restart the application or deleting all temp-files or after running all the CLEAR- and RELEASE-Commands.
>Sometimes reboot the PC solve the problem for the next session.
>When a browse-command fails, it fails always in the actual session, but other browse-commands in the same session may be ok.
>When a browse-command is ok, it’s always ok in the actual session, but other browse-commands in the same session my fail.
>
>The behavior is not really reproducable. In most (or all?) cases, the missed column is an UDF-column
>
>e.g.: browse fields item1, xyz=MyUDF(), item3, …
>
>Monitoring the UDF shows me, that when the browse fails, the UDF is called only 1 times by the browse. The parameters of the UDF shows that the first record is in access.
>
>In my tests I gave the browse-command with the name-clause an objectname and I saw in the memory dump, that the missed column also doesn’t exist in the Object.
>
>
>Any ideas?