Hi,

I created a new module which is a webform which the people at the callcenter at my company use. It can be used to register which customer has called, the reason he or she called and send notification by e-mail if the customer has to be called back by someone else inside the company.

All seemed to work well and people were very happy with it until some people started to lose data. People were working in the form and all of sudden when they clicked a button they would lose all data they had entered. The problem is that these instances appear to be completely random. It occurs at different times, on different button clicks and it doesn't matter how long the user has been online.

This problem is really driving me insane and people are starting to get agitated at the callcenter. Does anyone have any idea what may cause this problem? I've tried changing all the timeout settings in the web.config but it didn't do anything. Any help is much appreciated.

Ronald

Thanks for the reply.

1. In the course of filling out the form, how many times can postbacks to the server can occur?

I would say between 3 and 7 times. It depends on if they want to search for an existing customer, if they want to send the form by e-mail and some other options. I'm using 'panel' controls to hide/show the search options for instance and these require a postback.

2. Do you handle postbacks differently from non-postback?

Yes, a non-postback only sets some default options for the search function.

3. Did you enable v13wstat3 in the form controls?

Yes I did. The problem is that 99% of the times the form works without any problems and then all of a sudden someone loses their data. At any moment during the day there are people working at the callcenter who may use the form.

4. Does one need to login to use the module?  If so, do one get logout when the loss of data happens?

Yes they need to login to use the module. I'm using the authentication module to automatically log people in. I've turned on the server log to see if the problem was caused by people getting logged out but that doesn't seem to be the cause.

5. Why don't you add a save button?

I've included one but because it also does a postback it may cause the data loss. I was looking into using AJAX to solve this but couldn't get it to work.

6. Happens with all browsers?

We only use Internet Explorer 6 at the company I work for.

That's what I originally suspected myself. That's why I changed all the timeout values in the web.config and in the application. But it didn't do a thing. People could be working with the application for over four hours without problems while someone else might lose their data after only 10 minutes.

Also if people would get logged out and logged in it should show up in the server log, right? And I can't find anything strange there.

By the way, the authentication module I'm using is the standard one that comes with the latest releases of DotNetNuke.