Remaining data in ListBox

  • Thread starter Thread starter nartla
  • Start date Start date
N

nartla

Hello,

I am developping an application in VBA/Access (MDB file). To deliver
the app to my client, I create a MDE file.

The problem is that the app crashes sometimes, and then my client says
that he can see in the listbox of one of my forms several lines of
data that obviously remain from my tests. I mean that it seems that
when I create the MDE file, the Listbox keeps some remainings of the
data that was displayed when I was testing the app, and these lines
appear when the application crashes.

I wonder if this is a normal behaviour of the ListBox, and if it is
possible to remove this data before I create the MDE file and deliver
it to my client ?

Thank you for your help.
 
Hello,

I am developping an application in VBA/Access (MDB file). To deliver
the app to my client, I create a MDE file.

The problem is that the app crashes sometimes, and then my client says
that he can see in the listbox of one of my forms several lines of
data that obviously remain from my tests. I mean that it seems that
when I create the MDE file, the Listbox keeps some remainings of the
data that was displayed when I was testing the app, and these lines
appear when the application crashes.

I wonder if this is a normal behaviour of the ListBox, and if it is
possible to remove this data before I create the MDE file and deliver
it to my client ?

Thank you for your help.
Click to expand...


Sorry, the control when the "remaining" data appears is not a ListBox
but a ListView.

Maybe it makes some difference.
 
If you are setting the rowsource of the listbox at runtime, you might take a
look at its properties in design view. There may be a rowsource value saved
with the form. If working properly you would be replacing that value, but
maybe the crash is interfering with the replacement and your client is
seeing the data associated with the saved value..
 
If you are setting the rowsource of the listbox at runtime, you might takea
look at its properties in design view. There may be a rowsource value saved
with the form. If working properly you would be replacing that value, but
maybe the crash is interfering with the replacement and your client is
seeing the data associated with the saved value..

--
HTH,
George












- Afficher le texte des messages précédents -
Click to expand...

Thank you for your answer.
In fact, I am not setting the roswsource property of the ListView. At
runtime, I just insert strings into it by the mean of a AddString
property, or something like that.
 
Back
Top