Search results

yes, the eval field is what started this whole thing. I used it and it worked, (after a lot of help from here) but it wasn't pretty like this calculator.

One instance.... break a receipt apart into different categories and split the sales tax between them; light bulbs for the house, groceries for the hungry, a gadget for the ... Who owes me for this bill?... 30% is Bill; 10% is Jane; the rest is mine.

That one doesn't put your number where you want it either. In data entry, you call it, calculate, carefully select result, copy it, go to field, paste it. Have you ever done much data entry?

I downloaded the popup calculator Majp posted (who knew there was such a thing?). I like it but now I want to get fussy: 1. I set the equal button to default so I could press enter without it closing so I can see what the value is before accepting it. Doesn't work 2. Why doesn't the calculated...

What?! after all this trouble? You're a Philistine! Or something ;)

Majp... I would have NEVER, NEVER have figured out those little changes. Thank you so much. Made my day! I am so bad at this that the only reason I keep going is because I look on it like a crossword puzzle or sudoku. Tiny bit at a time!

Both. textboxes that contain fields called txtPayment. Default by Access. Would you change it?

Payment and Receipt are also fields. txtPayment and txtReceipt are fields on top of the others for calculations.

Majp... that compiles but when in the module I do this: Private Sub txtPayment_AfterUpdate() FldCalc Me, txtPayment End Sub txtPayment returns the value and not the field ie 100+150 "txtPayment" returns type mismatch txtPayment is the control name and also the field name

Private Sub txtPayment_AfterUpdate() On Error Resume Next If Left(txtPayment, 1) = "=" Then txtPayment = Right(txtPayment, Len(txtPayment) - 1) Payment = 0 Payment = Eval(txtPayment) txtPayment = Payment RetAmt Me End Sub Private Sub txtReceipt_AfterUpdate() On...

Gotcha!!!

ok. Is there a disadvantage to using a function over a sub? On further thought... I am manipulating the control. It depends on whether it's a payment or a receipt. I need to know. I have both a txtPayment and a txtReceipt. Thus, Case ctrl

Just so you know... I never completely understand what I'm doing and I'm okay with that. Some of us are doomed to be in a fog :unsure:;)You put way more time into this than I deserve and I very much appreciate it. Thank you so much.

Public Function FldCalc(frm As Form, ctrl As Control) On Error Resume Next Select Case ctrl.Name Case "txtPayment" If Left(frm.ctrl, 1) = "=" Then frm.ctrl = Right(frm.ctrl, Len(frm.ctrl) - 1) frm.Payment = 0 frm.Payment = Eval(frm.ctrl)...

It works very well. What I don't get is why a null value for year returns all years. I'll not fuss though because it works. Thanks for your time.

I have no field named "name" nor do I have a field named "year". You're suggesting I add a field "DataYear" in addition to CkDate? So then the field would need to be tied to the CkDate... So the field would be DataYear: Year([CkDate]) which is where I am already. I think I don't understand.

Well, it honestly didn't make sense to me but it does seem to work. Tell me what you would do, please. I would like the default to be the current year but be able to do all when needed.

Works! Really does! thank you!

Me again :confused: If I add WHERE (((Year([CkDate]))=[TempVars]![datelimit])) OR (([TempVars]![datelimit] Is Null)); This returns everything. I think I'm not using the null value properly.

Ok I changed the filter and it returns 2025 but I still can't get it to work in my query. SELECT [2qryRegister].TransactionID, [2qryRegister].CkDate, [2qryRegister].AccountID, [2qryRegister].AccountName, [2qryRegister].Num, [2qryRegister].Payee, [2qryRegister].Amount, [2qryRegister].PrintCk...