Edit Widget Errors - Data not being edited in real time...

[GeorgeHaskett]

Hello,

We are using 3.5 version of Viewer for Flex and ArcGIS Server 10.1, etc.

I recently created a mapping application via the Viewer for Flex and tested it out on my computer without any issues.  As of yesterday we are testing it with 3-4 users at a time.  They are using older 2GB desktops that seem to get sluggish rather easily when viewing applications on line, regardless if its my Flex map or Google Maps, etc.

We have had a few incidents where the app stopped working and data was not properly saved to the main database.  Isn't the Edit widget suppose to be updating the database as they make changes, so that something they did say 1/2 hour ago should be saved and not lost or scrambled when they computer becomes unresponsive?

What settings should I modify to help make things work more smoothly?

Basically I have 3-4 geocoders working at a given time.  I currently have one services published to use within the Edit widget.  The service is then queried out to create a unique operational layer for each person in question via the Expression attribute under the layer element.  The data is coming from an IBM DB2 SDE database that has been Enterprise enabled and registered as a versioned SDE database.

Why is it crashing and why is the data not being regularly updated?

Any suggestions?

Thanks

[GeorgeHaskett]

Expanding upon my previous post...

Is anyone currently using the Edit widget in a multi editor environment with success?

If so, what are the settings you are using to do so?

[GeorgeHaskett]

Need to bump this back up.  I could really use some assistance on this one.

Is anyone actually successfully using the edit widget?  If so, what settings are you using to do so?

Things seem to work okay when it only one user, however issues appear with multiple users....

[BjornSvensson]

George, I haven't heard anyone else having that sort of issues with the Edit Widget.  You might want to contact Technical Support and work it through with them.

When you edit features with the Edit Widget (or AttributeTable), they get saved right away.  You can look at the http traffic to make sure there is no error thrown when it gets saved.

[GeorgeHaskett]

Thanks for replying.

I will contact Tech either today or tomorrow to verify my settings.

Are you familiar enough with the preferred settings for the Edit widget?

From what I can gather, the following settings may have an affect on how the widget functions:

ArcGIS Server Settings
[INDENT]Max number of records returned by server (1000)
Enable ownership-based access controls on features (Unchecked)
Max time a client can use a service (600)
Max time a client will wait to get a service (60)
Max time an idle instance can be kept running (1800)
Low vs. High isolation (High)
Recycle Settings (1hr)
Health Check Settings (5min)[/INDENT]

Viewer for Flex Settings
[INDENT]autorefresh (60)
disableclientcaching (true)[/INDENT]

Should I alter any of them or should everything work fine with the default settings? 
The settings in () are the ones I am testing, I am hoping to test against data in both an IBM DB2 and SQL databases.  When we originally ran it we were using the IBM DB2 and that's when we ran into so many problems.

Any suggestions would be great.

Thanks,

Haskett