Search results

This seems the best solution to me.

Or can we just add the [code] tag to the Quick Editor bar?

Have you tried a calculated field set to Format([ShippedDate],"mmm")? Or "mmmm" for more than just the first three letters.

You can spoof the field names or whatever for confidentiality, but without seeing what you are TRYING to do, we can't really help you. You suspect the field names have changed... but have you checked??

Hey OKlahoma! I went to college in Norman at OU...

Did you verify that the query/SQL that your form is pulling from includes the new field? That's a frequent tripping point.

Your screenshot is awfully small... Does each site have a specific number of workers (on a given day), or will the second checkbox apply to all sites? I'm kind of assuming the former, which leads me to ask, will they assign one worksite, then go on to the next? Walk us through the process a...

Hrm. Could you save the 'email' as a PDF report instead, maybe? Or one of my processes emails an Excel spreadsheet, so it saves the spreadsheet in a central location, and we rely on Outlook to store the data about the actual email and attachment.

Not without a lot more information. What does your form do? Does it run a Macro or some VBA code? Post the code/macro and we can help debug it, but all you've said right now is "it doesn't work!"

Lots of Missouri folks lately... and yeah, this week makes up for the 2-degree weather we had a couple of weeks ago.

I think what spike means is that it will depend on where the querydef goes... if you're trying to resave it as the new 'stored query' until someone changes it again, that takes one method. If you want them to put in a TOP value and use that on the fly for this current run, that can be done...

Unit will be a calculated field, not a stored one. =Int(([TimeField]+59)/60) & IIF([TimeField] Between 1 And 60," unit"," units")

Glad I could help with most of it. The other thing you might try is to delete the CONTROL (not the table field), compact and repair your database, then re-add it and your input mask again. Something seems to be goofy in there but starting the control from scratch will probably restore it to good...

OK! I never promised you pretty code, but this seems functional.. obviously work on a COPY of your data first (you have the text file to reload, but stilll...) Option Compare Database Option Explicit Public Function BruteForce(Optional a As Long) Dim rs As DAO.Recordset Dim CustID As String...

0) Really bizarre. I also added and removed the input mask from your table, but that shouldn't have had any effect. You might try it anyway... save and backup first! 1) Option Explicit is good coding practice - it means the VBA editor will warn you more often BEFORE you run code that is likely...

I have not forgotten you, but work has exploded this week. If someone else can figure this out I welcome them to take on the project. Essentially what I'm thinking is (and this is for other VBA coders, not you lliozzi unless you know a lot more VBA than you're letting on :p) to add a new...

Okay, so I got a chance to look at your uploaded database. It definitely did the double-keypress thing, but I got it to stop by wiping out the Input Mask, closing and saving the form, then opening it up again and reentering the Input mask. I still have no idea why it was doing that. For...

It is the control on your form that you have named [File Name]. So Private Sub Form_Current() If Me.NewRecord Then Me.File_Name.SetFocus End Sub

Always bind your controls directly to a table/query if you can. APPEND queries take longer to run, are more prone to error and harder to debug. What I would do is just have a small continuous form with three controls side by side: Combobox that is BOUND to tableBeingLate.EmplID, but has...

I think I can think (heh) of a way to step through that whole long file and drop CustID into a blank field between ID and Date (don't name fields just Date by the way... I assume your real table is different, but that's a keyword in Access). I'll try to draft something up on Monday, though...