Search results

You should have tried looking at the report’s rexordsource in datasheet view. Nulls would have been apparent.

@Imb, when are you going to post full documentation or a sample application file since you seem to be pushing your solution on a frequent basis. Maybe set up a zoom call for some of us to actually view this "dynamic" solution. If not, it does absolutely no good to read your posts.

Ken, in all my decades of Executing SQL statements, either I wasn't aware of that "feature" or forgot it decades ago.

I would make sure the Lvl# fields are in the report's record source and included in the GroupHeader1 as bound controls. They don't need to be visible. Then, open the report's record source in datasheet view to make sure the Lvl# fields are valued (no nulls). Then, this code in the...

I’m a bit afraid to ask but could you share the relationship of the connections database?

Can you assure us the record has been saved? Also, are the Lvl1,… fields are bound to controls in the section with the image controls?

CJ, can you explain your code? Maybe you know something that I don’t which is quite possible.

Report sections have an On Format event that should be used to set controls visibility within that section. I would try something like: Me.[Lvl1Img].Visible = Me.Lvl1 Using numbers in field names raise a red flag regarding normalization. Do you have Lvl2,…

To each his/her own. If I have an employee table, ever field in the table begins with emp. The auto number primary key is empEmpId. The foreign key fields begin with three letters identifying the table followed by three letters from the related table and “Id”. I love not having to think about...

I learned a long time ago (but not soon enough) that sometimes you need to simply accept someone’s opinion of you and move on. Change what you have the capacity and desire to change and be the grownup in the room.

I mentioned this forum about a year ago to a very well-respected Access developer and he/she stated the forum was avoided because of the contentiousness. Maybe others avoided participation for the same reason. I have had a few moments where I considered buggering off for that reason only.

With your original code all you would have had to do to get around your error was to set a break point and step through your code. That's why you should have structured your code with Select Case like: Select Case Me.cboqueries Case "FILENO" Me.lstsearch.RowSource = "qryFILENO"...

Wow! A question asked and within about four hours there were seven great answers from our pool of volunteer experts. Kudos to this site and all members (those who ask and those who answer).

Replace the multiple If Then statements Select Case.

Do you have contracts without a related customer record? Is there a default value in the Customer field of the contracts table?

Your post mentions "SpecializedAssignment columns, Active (checkbox), and columns Month/Year columns". This implies you are storing data as field names which goes against normalization. For instance, if you have column names like "DaysTardy", "DaysExcused", "DaysNotExcused" then you are creating...

My wife has drug me into watching all of these.

Ken, it’s a bit suspicious that you have such a deep understanding of these laws 🤨

Do you get intellisence when typing DAO.

The calculations the production supervisor wanted me to use were wrong creating higher bonuses. I’m not sure why I was let go, if it was because I found his error or I found his error 😁. I also avoid using yes/no fields since the future holds lots of “maybes”.