Recent content by Jhart22889

WORKS PERFECT!!!! Thank you!!!! I think I may stick with the command buttons as It may make things a lot more simple than adding the report names to a list box and having that call the report.

I actually used an on open macro and set the where property "ProjectID="&ProjectID. I figured it wasn't in the proper place I just wasn't sure where to put it.

Hi I actually have a similar problem, I want to have a summerized report that opens idealy when the report option is selected in a list box (there are 4 reports that will show different totals all from the form with the Project ID being the connection to the information). Right now I just have...

I fixed my problem, a combination of Case statements and the "debugging" code provided help alot thanks guys.

I've tried all of this and the procedure is "still too big"....can anyone assist in the right direction for maybe a SELECT Case statement?

ChrisO, I've added this code (tried under the main form and the actual subform) and set the tag properties to Hide but the columns are still visible so I've hard wired it into the main form's on load event for the columns to work and began conditionally unhiding the columns which works.....the...

so with your solution mdlueck I can essentially keep the code I have the exact way that it is?

MSAccessRookie, I agree that the specs aren't even close to the max limitations but I'm not familiar with Select cast statements but I think that could be an option, I would assume the datediff would be the case and count the number of days up to 365 but in monthly intervals like I have...

I think what i'm looking for is a way to cut down on the size (or amount) of the code. I'm not sure decompiling would help.

I have some code that allows fields on a form to be show or hidden based on the start and end date chosen. The code is called through the after update of the end date. I've also tried creating a module with just the hidden/not hidden criteria and calling the module with the if then statement...

Not quite, originally I had the information split into two tables, those in the single form view in one and the datasheet view subform information in another....I compiled them because it is similar information all pertaining to purchasing and would help when trying to create the desired reports...

To simplify things, the third subform that is used in datasheet form only allows me to put in one record (one row) and doesnt allow me to click in a new row to enter any data in it. I want the code to move the cursor (focus) back to the first column after finishing one row to enter more data.

Hello all I have a dilemma with some code that creates table entries from multiple subforms. There are three subforms that are based on one table, two subforms are in single form view as they only require one entry per project however the third subform is in datasheet view and has the ability to...