Search results

You can always add some simple VBA code to loop through the unique departments to build your crosstab SQL statement. I do, however, reserve the column headings mostly to date related values since most of my crosstabs are record sources for reports.

I would create a query with this SQL to show all your import/export specs SELECT MSysIMEXSpecs.SpecName, MSysIMEXColumns.FieldName, MSysIMEXColumns.DataType, MSysIMEXColumns.IndexType, MSysIMEXColumns.Start, MSysIMEXColumns.Width FROM MSysIMEXColumns INNER JOIN MSysIMEXSpecs ON...

From my experience, parameter types are NOT always required when referencing a form control in a crosstab query. Setting the column headings should remove the requirement. This of course will only work when the column headings are known, static values like months, days, numbers,etc. for...

You can’t post URLs until you have posted 100 times. This includes replying to a post that includes an URL. I used a lot of posts welcoming new members 😁 to get up to 100.

I would change the SQL of a saved query in code just prior to opening the reportUrey would be the record source of the report and would filter as desired

There are lots of videos etc if you search the web for “ms access audit changes data macro”. I expect some allow for multiple fields

You can see if they experience issues if they set the printer to PDF.

Did you attempt the method I suggested with creating multiple columns from a single field where one of the multiple will have the value and the others will return 0?

4:06 and 4:11 are not hours worked. These are both decimal values under the hood that store the amount/part of a day where a day (24 hours) = 1. The value 4:06 is actually stored in your table as 0.170833333333333. Noon has a value of 0.5 while 6:00 AM is 0.25. Your results might be confusing...

I've been on a couple trips. Can you build a query that has the User/client, Standard Action, Challenge/Day Type, Date, and the numbers displayed? I don't need or want the [Days by Week] whatever that means.

Check the form's data properties. Data Entry should be set to "No". Setting it to "Yes" allows you to enter new data without viewing existing data. If this doesn't match your situation, you might want to view other data properties including the Record Source.

It seems you are attempting to store a text value in a numeric field. Rather than a Value List, consider using a small lookup table to store the drop-down values. These tables typically have a numeric primary key (autonumber) that gets stored in the main tables

You can either calculate the values or reference the form and control in a text box on your report like: Control Source: =[Forms]![employee details].[First Name]

You are a better mind reader than I am 😊

Are you suggesting you can’t use a report grouping to calculate aggregates or are you referencing @June7 post? You can’t use an aggregate function in a header or footer based on the name of a control in the detail section but you can use fields from the report’s recordsource.

Typically you would group your report by employee and date. Add a header or footer for this grouping to display the sum of the time worked. As June7 suggested, there could be issues if shifts span midnight.

But you said you can’t make decisions about splitting until the database is finished. Apparently you will never split and quite possibly never deliver a working application that will be worth all the effort you are putting into it.

Your database will never be finished (I had to control my urge to type that in BOLD, ALL CAPS)!

Sorry, I had simply read the misleading title.

You may need to set an attribute to save the password. Check out Doug Steele's function for the "Addendum 1".