Browse EIP drop gen recod not available

[Alberto]

Using EIP drop with only manual options generates error 33 updating the file.
It works ok if you use a file for drop options.
Im sending you an email with the example

[Bruce]

excellent. Haven't got your example yet though. make sure you send it to the right address...

[Alberto]

sent it to you using alberto-michelis@hotmail and alberto.michelis@gmail

[Bruce]

what address of mind did you use? bruce dot johnson is the one that gets to me...

[Alberto]

Im using this, I always sent mails to you to this address, may be its in your spam? or you are rejecting mails with attachs of more than 20Mb?
Willl send you again not using  atachments but links.

[Alberto]

OK this is the scenario and the problem.
NT server running in my PC, connected to a MsSql server far from here and with slow internet connection.
Why this? to test and avoid deploing each time I make a change in the NT server.
Problem is that when using any type of EIP in a browse I get an error 33 message from the server.
Just FYI
Regards

[Matthew51]

Is the browse getting 2 refresh events very quickly? This happened to me recently. I had 2 browses, the second had an epi button and would refresh the first when accepted. When a user clicked the button a rowClicked and an eidAcceped event would be sent to the server very quickly causing some of the _bidv_ values to become invalid.

The solution for me was to go into the from containing the browses and change the case statement to ignore the rowClicked event.