Recent content by ersocia

thanks for the link. however, as i previously stated: i didn't create the DB that the linked tables are stored in. i'm basically recreating it from scratch elsewhere, fixing the unbelievable amount of poorly designed forms/queries/reports/tables, not to mention weeding through a mass of...

i certainly appreciate the effort :P i did check tblautoinfo, and the information in there is correct. however, i did also notice something about tblautoinfo: the [First Name 1] and [LastName] columns are lookup columns. that's the only difference/inconsistency i can see. maybe the update...

put in QUOTE tags because in CODE tags it shows as one continuous line requiring some scrolling to read it. below is almost exactly as it appears for me in SQL View. (and as an FYI: the linked table was not created by me, nor do i maintain it, so the bad naming convention is not on my...

unfortunately, that would require me stripping out all sensitive data about our residents from all of the tables. not to mention the fact that the linked table involved wouldn't be able to be included, and it's integral to the issue at hand. all that aside, i'm actually at work right now, and...

the table that this Update Query is supposed to modify ("Automobile_Info") contains the three fields "Suite", "FirstName_1", and "LastName" (among others). there is a linked table ("tblautoinfo") which the Update Query is getting it's modifying data from, which also contains those fields. i...

i'm still pretty new to all this as well, but looking through my code and the way it's laid out, could this fix it? my guess, which could very well be incorrect, is that without the addition of the "error_exit" procedure and a call to it after the error message is displayed, the program...

in this particular DB, "inter-form communication" won't be necessary. there aren't many forms, and the ones that do exist are simple data entry forms that have no need to interact with eachother at all. granted, i could very well still be completely misunderstanding what you're all talking...

sorry. i'm still lost. from what i can gather, you're talking about ways to do far more than what i was looking for, which was simply to have a piece of code to check whether or not any form other than the main one (switchboard) was open. i did not need to pass information either to or from any...

thank you, and i appreciate the suggestion, however: 1) i didn't completely understand what you are trying to explain here. 2) i went with DJKarl's last suggestion to use "Application.Forms.Count", and that did exactly what i was looking to do :)

eureka :) If Application.Forms.Count > 1 Then MsgBox "Updating tables is not recommended while Data Entry form(s) are open." & vbCrLf & "Please close any open Data Entry forms and try again.", vbCritical Else DoCmd.SetWarnings False DoCmd.OpenQuery "UPDATE_RES_INFO_TABLE"...

please disregard my previous post. i've figured out how to call the newly created function. If IsFormOpen("<Form Name>") = True Then ... Else ... End If however, it still doesn't quite do what i was hoping for, as i still need to call the function multiple times to check for each individual...

thanks for the suggestion :) two things: 1) while i imagine this would indeed reduce the amount of code necessary, doesn't it still involve passing each form name individually, rather than simply checking to see if any form is open? (in other words, it doesn't matter to me which form is...

so, i was just reviewing some of the most recent changes i've made to my DB here at work, and when i reached this piece of code, i started wondering if there's an easier, more compact way to do this. don't get me wrong, the code definitely works, and works well enough, i'm just curious for...

oh, i doubt i'd be surprised, as i'm usually more of a "search for an answer from somebody who already had this problem" kind of person, rather than a "post the question myself" kind. :P so i know the importance of posting the solution to your problem when you find it, because i'd only get more...

i actually did all three of those things yesterday when the problem arose, but without incident. couldn't find any issues when doing so. however, thanks to your PM, i've sorted the problem out. for those interested in what fixed it, i simply created a new, blank database, and imported all...