Refreshing Forms

[krazykaigh]

I am using Access 2007. I am designing db that inputs client information and outputs a Last Testament and Will as a word document.

I have one section that takes specific bequests: I want my son, Jimmy Lastname to get my onyx bracelet. However if Jimmy fails to survive me then I want Markee Lastname to get it.

Jimmy would be the primary beneficiary, Markee would be the alternate.

Here is where my dilemma comes in. The subform sbfrm_SPC_Inherit (pictured in Will_DB attached) has two subforms on it: sbfrm_SPC_Prime and sbfrm_SPC_Alt, respectively they hold the primary and alternate beneficiaries for each item in tbl_SPC_Inherit (sbfrm_SPC_Inherit). Now as you may see from the screenshot, when a user first comes upon the form it show "New" in Specific textbox. The two subforms are both locked. When something is entered in Item the record "comes to life" (record number assigned).

Now, my problem is in validating. If someone enters data into Item and then decides to erase it (backspace or deletes entry) thereby leaving a NULL or "" value, I am message boxing user that since nothing is entered this record will be deleted. When I delete using VBA code (attached), I get the dreaded #deleted, making that record unusable until either I refresh form (using ribbon) or .requery (this can cause hang).

Now what I am noticing is that if an entry is made in Item and then deleted/backspaced and I don't enter either beneficiary subform the record is not deleted. However, if I enter something in Item and tab to or click in either subform, and then go and delete the Item entry, my form deletes the record and but doesn't do the requery.

Any suggestions will be analyzed, may be used, but will definitely be appreciated!

Oh, I am also thinking of having the Will Fill portion just id any incomplete information and ignore rather than correct on the input.

As a side note:
I have found making grammatically correct sentences from data that has multiple possibilities of entries is both fun and time consuming. And in a Will it is oh-so-important to have EVERY sentence a model of good grammar (or well grammar... whatever, haha)

 

[krazykaigh]

@Pat Hartman

Thanks for that. It works for the most part...

There are quirks, like the .setfocus throws an Error 2108, must save record before .setfocus may be used. So I just made .value = .oldvalue and that seems to help.

I think I have to do something on .Lostfocus also for field confirmation cause someone can simply click outside of the subform(which is just another control) so I had to do a form .exit event also.

It's like each fix finds a new leak...

Question why did you suggest making Prime and Alt .visible = false over .locked = true? What are the benefits?


Anywho, thanks for the point in the right direction