Recent content by Jared

DCrake - Changing the code to just strLeftName, strRightName, and strHyphenLess eliminated the runtime error, but put it back to always equalling zero. Lagbolt - Simply using the bang instead of the period fixed it perfectly. When I was posting this, I figured it would end with a "d'oh!"...

I do see the difference, but when I implement that code change, I get Run-time error 438: Object doesn't support this property or method. I'm running Access 2007. Could this be a setting problem?

I am quite sure I am missing something very basic, but I've been struggling with this all morning and am hoping I can find some help. I have a form, frmPersonnelFlexible, for entering personnel records. It's largely based on a table called tblPersonnel, which has PersonnelID as a unique record...

Summer - I have gotten a lot of help from this forum just by reading, so...it's time to give back! I happen to have cobbled together an answer for your problem yesterday, based on code from a number of sources on these forums (notably BobLarson and Jacob Mathai), plus a little bit of my own...

In the thread regarding the Conc() code put together by Jon K (http://www.access-programmers.co.uk/forums/showthread.php?t=64611), you mentioned that it worked perfectly in Access 2007 once you updated the VBA ADO references. Could I get a look at your modified code? I really liked the Conc()...

Ah, so with the button setup you recommend, clicking each button just changes which subform is actually present? That probably is a bit more elegant, as the code in the subforms then actually isn't present to interfere with each other. It sounds like it might make the database a bit less...

I've put together a fairly complex personnel database. The most complex part of it is the main personnel form: there are so many pieces of information that might be entered for a given person that I've broken it down into one main form with the person's name and roles in our organization, with a...

Oh, I'm a not-IT person sitting in my cube constructing a massive Access database. I'll be back with more questions, no doubt.

Yep. Again, thanks to everyone for the help.

To not let this be one of those threads that peters off into nonexistence with no clear resolution: I simplified the query (extremely) and built the necessary subforms, and the new form works, to the great delight of all in my office who wouldn't like to watch me hyperventilate myself to death...

I was referring to them as inelegant because I thought using several of them was a brute-force method of doing what could be done more simply with a single form built on a properly constructed query. (In the training courses I've taken, I was told that most forms are built on queries and...

Larson - Thanks, but I was trying to clear all the data except a few records that might provide relevant examples. Thanks for your patience. I am really hoping there is another way of doing this than a half-dozen more subforms. I can do it, but that'll be...inelegant, let's say.

I will try to post a stripped copy within the next half-hour.

Access Hero - It looks like mine falls under "It uses JOINs of different directions on multiple tables in the FROM clause. Remove some tables." I can build subforms to allow the data entry. It's just going to take a lot more work. I had thought that the structure error was entirely on my part...

I have made those changes, but the query still blocks data entry, as does the form based on the query. I understand that I have very limited expertise with Access, and there are undoubtedly a number of ways in which my database can be cleaned up, but I have under two days to get it ready for...