Search results

Also, I have had issues in the past with larger image files not rendering. Do you know the size of the files and have you tried with smaller files? I would also add a line in your code to help troubleshoot: Debug.Print CurrentProject.Path & “\img\” & Me.txtPathImage

I found your images confusing. It seems that your field in question is a lookup field and behaving like lookup fields behave. You would almost always want to use and store the ID value, not the text. The text value is stored only in one table based on sound relational database theory.

I would place a breakpoint in the code so the values can be seen by hovering the pointer over your code. Also, use Me.[CheckBalance]

I think you forgot the S tblEmployees. I would question the join on a field where I can’t imagine being a primary key in either table.

Can you open the mdb files?

I would use a data driven solution (maybe a couple lines of code) where the number per day and times are stored in related tables. A plan with twice a day at 8 AM and 8 PM become a record in tblMedPlans with two related records in tblMedPlanTimes with TimeOfDay of 8:00 and 20:00. There is also a...

As long as the subform allows additions 😉

Can we assume you aren’t referring to the line at the bottom that displays default values but isn’t a new record until you modify any field in the bottom line?

Yes, it was #9 which I wrongly assumed was the table datasheet rather than the datasheet of June7 query recommendation.

So the fields actually are numeric and store 0s. Zeros are values, not blanks and the should not be compared to a string.

If the salary is numeric, remove the quotes from around the amount. I would also delete the inner ()s.

I would set the Where clause to; WHERE Trim(fld1 & fld2 & fld3 & fld4 &"")=""

I recall a support call from client at least 20 years ago with a larger monitor. I had code that automatically set a subform width based on the main form’s InsideWidth. I had to modify the code to accommodate the issue.

Is this a standard text box? Is there code in your form that provides the autocomplete functionality? Is your directory/folder trusted?

I agree with June7. I started writing the code on the form to modify the SQL and then realized it wasn't necessary if the expressions and a data value were changed. LeoM, your VBA hard codes in the values of Owner, StartDate, and EndDate while also locking in the number or heading groups to 3...

If you use my recommended solution, you can change the crosstab column expression to: Expr1: [Seq] & "-" & [CrosstabHeading] which will group the dates and owner columns together for each "event". To make it even better, change the value of Start Date in the crosstab heading table to Begin Date...

You could take my solution and add "Owner" as the third record. Then make sure the OWNER field is in qselSubSystems. Change the SQL of the crosstab to: TRANSFORM Min(Switch([CrosstabHeading]="Start Date",[STARTING_DATE],[CrosstabHeading]="End Date",[ENDING_DATE],1,[OWNER])) AS Expr2 SELECT...

You can get rid of the Column Headings property values. It was there as a hard limit and also sets the column order. I think the subform will display any number of columns up to Access limits.

You can create a crosstab with pairs of values (Start and End) by creating a headings table [tblCrosstabHeadings] and adding to values I use a ranking/sequence query [qseqSubststmes] to generate the 1,2,3,... SELECT tblLeoM.Subsystem, tblLeoM.STARTING_DATE, tblLeoM.ENDING_DATE...

I don’t believe you have ever stated where you are creating the file? From your permission screenshot, I would expect to see full control.