Search results

Watches might make a comeback in all the schools that are banning the use of cell phones during school hours. Ain't it great? Invest in watches and learning Access. I'm glad I jumped onto the Access learning train yeas ago, but I would still learn it all over again if I had to.

Knowing how you approach this exact issue Pat is very helpful. Thank you.

That makes sense Pat. I just never seen the code for this logic before. The thought of using a flag like variable crossed my mind, but I just wanted to see what my options were.

That's what I was looking for @MajP. I see that checking for all the validations in a separate function and only if everything passes, then close the form. I think Josef P.'s idea would work as well.

No, that's not what I'm looking for as I am aware of that solution. I will have many more complicated validations to contend with.

I'm trying to do a simple textbox validation to test if the description field is filled out in a very simple test form. This works when using simple code logic, but if using my close and save button, the form closes before there is a chance of correcting the problem on the form. So then I put in...

OK, now I see what was going on with the 2046 error. The text to be copied must be highlighted or selected before that command will be effective. So an even better way if using the double click event is to simply set focus elsewhere first then back to the target textbox. This ensures the entire...

Not sure what the difference is, but the new code does work. Simple is always better.

No, I used a double click event on a notes field. There was text in the field and that's the error I got after double clicking. Arnel's method worked perfectly.

I got the following error using that technique.

You might have to Browse for the FM20.dll in order to see that reference @arnelgp pointed out. It wasn't there for me until I browsed for it.

Thanks for the added explanation.

This thread is very disturbing if true. Especially the part about unbound control on a form cannot be referenced. I just tested this and didn't have a problem. What are the test conditions to confirm this?

Please see june's post #29 for example of what i meant. Im not saying references outside the query.

Try this.

What was confusing about it. You CAN reference the value of an alias in a query as was just demonstrated in the last few posts. Wait, I may have updated my post after you read the initial one. Maybe that's where the confusion came in.

I didn't word that correctly, was focused on the use of Quer1 in the Quer1 itself which is not possible. Referencing aliases in the same query is possible. My mistake.

Here is what you were trying to do, but as MajP pointed out, there is no way to differentiate the normal order items from the rollback items unless you change the structure of the table as he already laid out for you. INSERT INTO tblLineDetails ( InvoiceID, Quantities, SellingPrice, ProductName...

This is your only option to get the effect you were going for. Get used to it.

Here is what Philipp recommends over at codekabinett for books on Access. Even though these books appear to be outdated, the information at a basic level will apply to any of the modern versions. Of course the interface looks different between the 2010 version and todays modern ribbon interface...