Search results

I don't know. I am using 2007. If the date function is working in the rest of 2000 then it should work in VB too. Maybe try getting rid of the parenthesis after the date. So just Me.ControlName=Date If that doesn't work: make sure you are referencing the control name in your code and not...

Is "Chain" an ID field?? Sorry should be: DoCmd.OpenForm "frmWWLiveTbl", , , "[Chain]=" & Me.cboChain

So, you are opening the new form from the current form? Try this: DoCmd.OpenForm "frmWWLiveTbl", , , "Chain=" &Me.cboChain Make sure that cboChain is the correct control name.

It sounds like you are trying to add a record to a child table before adding the record in the main table. This is why we use subforms... Other than that, it is hard to say what is going on since there are no tangible details. We have no idea what your table structure is or what the record...

By the way, this should have been posting in the forms section not in queries...

Where is the default value being set: in the form or in the underlying table? Try doing it in the table instead of the form maybe and see if that helps. If that doesn't work, then you could use code in the subform's BeforeInsert to set the value that way it will only be set when the user...

Yes, something like this is possible with some basic code. Your question makes it sound as if you want somebody to walk you through the design of your entire front-end. Hopefully this was not your intention. You seem a little confused about queries or maybe I am not fully understanding what...

Or a split form may be more appropriate in your situation if you really need to use a single query...

What is the recordsource of your form and subform? Based on your question, it sounds as if you are using a single query as the recordsource for both the main form and subform, which is not how this should be done. To be honest, it isn't possible for any of us to figure out what is going on...

Make your button and use either a macro or code to output the file to PDF. A macro may be easier if you aren't familiar with code. To do it with a macro, select your button and go to the events tab. Then select "output to" as your macro action and follow the steps (basically all you have to...

Thanks guys. Ideally, I would like to tell it to start a new page if two groups cannot fit together on a page but I will try making these adjustments and see what I can do.

Hi Goh, Thanks for your reply. Yes, I am using groupings. I know how to keep one group together but I need two groups to stick together so that the page doesn't break in the middle. Sorry this wasn't entirely clear... Is this possible?

Is this possible? How?

No problem. The control name vs field name thing takes some getting used to. Rest assured that many code issues posted on here stem from that problem. Good luck!

Your question is kind of vague. Plus this should be posted in the code section. If you want to refer to check boxes, you refer to them like any other control: Me.ControlName. In Access VBA check box values are -1 for yes and 0 for no, I think. I don't use check boxes in Access because I...

Ok, so try the above solution. I think it will work. If you have problems post back.

For some odd reason, I was thinking about this question while swimming last night and realized that we never suggested that you try to do a count on the field in a totals query. That would be worth trying if you are still seeking a solution to this issue.

Do all the customer ID #s have 4 numbers preceding the letter? If so, you could try making a calculated field and trimming the first 4 characters. So something like this: CustIDGroup: Left([CustomerID],4) And then group by the calculated field

You need to refer to control names in VBA, not field names. To check your control name open the form in design view and look at the Other tab. The Name listed is your control name. You shouldn't need the brackets at all. If you start typing Me. the intellisense should show you the available...

Wait I noticed one problem: you need a primary key field (autonumber) for your junction table, so EmployeesEquipmentID or something