Re: Data collisions

Andy_Khosravi@xxxxxxxxxx wrote:
> I'm having a bit of a nuisance problem with my A97 application, and I
> was wondering if any of you might have any ideas on how to get around
> it.
>
> The setup: I have a large main table (call it tblBenIssue) that has
> around 30 unique fields. In order to avoid over cluttering the form I
> generated from that table I organized the fields into topics, and then
> created separate forms for each topic (call them frmNtwks and
> frmRecovery). Each of those forms links from a main form (call it
> frmBenIssue) that contains the basic BenIssue header information. All
> of these forms have the same datasource. Also note that ALL of these
> forms have subforms (which all link to different tables).
>
> The problem with this design is that the user has data collisions with
> themselves sometimes when they edit a field in one form, close it, and
> then edit a field in another form. (They get a warning MSG box that
> indicates another user has modified their record before they saved
> it). Apparently the same user has the same record open twice in edit
> mode.

Use a simpler design.

Use one form but use a TAB control or something to simplify the number
of fields on screen at one time. Or use one long form with page dividers
and use buttons to navigate between pages. Or close all the forms but
the current one so you only have one open at a time.

> I realize at this point that I should have probably broken up the main
> table into several smaller tables with 1 to 1 relationships, but I'd
> really rather avoid that at this point as I'd have to change a lot of
> other things to accommodate this.

I don't think there is any need for that here.

> So, I've been working on trying to avoid the problem of a single user
> having the same record open in edit mode twice with VBA. I thought
> that executing a save record command on the form open buttons (before
> the docmd.openform) and on the form close events would take care of
> the problem. Unfortunately this is not the case (although it does
> seem to make it occur less often).
>
> I'm wondering if there is something else I could try to force a record
> out of edit mode so that the update collision does not occur.

Simply don't open the same recordset more than once at a time. Change
your form design.
--
regards,

Bradley

A Christian Response
http://www.pastornet.net.au/response


.

Relevant Pages

  • empty form feilds
    ... My problem is that the form i design when the data entrey emplyee open ... the form the old data appears so they edit the old one with new and ... employee opens the form the feilds be empty in order to avoid any ...
    (microsoft.public.access.forms)
  • Re: Test Driven Development
    ... We do not write production code until there is a failing test. ... * WRITE A TEST that will only pass if the ability is there ... * When the tests pass and you get a Green Bar, INSPECT THE DESIGN ... there, or one more edit to make there, then we must perforce be able to ...
    (comp.object)
  • Re: Do You Have to be a Learned Musician to Like Tristan?
    ... only edit the regional prison. ... As entirely as Roberta picks, ... avoid the unit much more notably. ...
    (rec.sport.hockey)
  • RE: Trouble updating gridview with storedproc
    ... I have implemented the Edit & Delete buttons as template fields because I ... When I click the Edit linkbutton, my RowEditing event handler does fire. ... The second time I click the Edit linkbutton, the grid does go into edit ... When I click the Update linkbutton, the grid never exits out of edit mode ...
    (microsoft.public.dotnet.framework.aspnet.webcontrols)
  • Re: Document List - links still shown for users that dont have access
    ... This is "by design" - the design being that access to the actual document ... > Have created three doc libraries ... > 2)"Docs only for developers" ... > developers@xxxxxxxx View, insert, edit, delete items ...
    (microsoft.public.sharepoint.windowsservices)