I have never run into this before.
It may be too late to asked.
What was in the log when it failed if you turn all the debug levels of the log on?
Was there any database errors?
Have you try to recreate the listbox again from scratch and delete the old one?
May be there is something in that listbox in the project that is corrupted.
"Kelley Foust" <[EMAIL PROTECTED]> wrote:
>
>I have been chasing a problem for 3 months that I finally figured out. We had an
application developed in 4.1.2 that used SQL Server 6.5 and Access 97 as a
backend
and was deployed on NT 4 SP5. When we ported the app to 4.1.3 it stopped
working.
I finally figured out the population of a listbox was what was causing the
app to
timeout execution. This ListBox was being populated by a dataobject that was
hitting
a SQL Server table. We were using one of the fields as a value and three
other fields
>as the label. If the ListBox was populated by manually executing the Bound Dataobject
and the fields manually added (not doAutoFill but addSelectableItem())
everything
finally worked. I am now curious if anyone else has seen this behavior?
_________________________________________________________________________
To unsubscribe from this mailing list please send an email to:
[EMAIL PROTECTED]
Please remember to use the same email address you subscribed with.
For help in using, subscribing, and unsubscribing to the discussion
forums, please go to: http://www.netdynamics.com/support/visitdevfor.html
For dire need help, email: [EMAIL PROTECTED]
