Search results

Hi. Welcome to AWF!

Hi Frida, I offered my assistance to Barbara, but I didn't hear back from her.

I have run into that warning but only while in dev mode. I have never encountered it on a production copy.

Ah, but that wasn't the process I asked you to do. I merely said to hit Ctrl+G and didn't say to open any form. So, I guess you don't get an error if you did what I asked then, right? Still, a demo file would really help make things clearer for us, no?

Supposedly, when you open the app using the shift bypass, no procedure should be running, so you seem to have an odd situation going here. Are you able to post a sample db to show this problem?

Can you open the file in shift bypass mode and still get the error when you hit Ctrl+G?

Did you check if there's Conditional Formatting applied to it?

Quick question: What is the name of the field that you were deleting when you got that error?

This error appears to be a result of your VBA code. You'll have to show us that part. You can modify it to either check for nulls or auto change nulls to something else. For example, you can use the Nz() function for that. Did you try the Before Update event? That can't be right. Access should...

Hi. Welcome to AWF!

Take a look at this one. https://www.access-programmers.co.uk/forums/threads/scan-muli-page-document-in-access-database.246348/page-2#post-1317909

Hi. Welcome to AWF? What kind of examples are you looking for? Didn't you already get an example from the second post? Are you looking for a tutorial or a link to a video? Or, are you asking for an Access database that does the document scanning? If you don't know how to code, there is a way...

Oops, forgot about that. 😆

If you still need help, consider posting a sample db showing the problem. Do those "valid" fields happen to be lookup fields as well?

On which line?

What is the "scheme?" Do they get a point every time they log in? So, if they log in and then log out and then log in again, they get more points?

Hi. Welcome to AWF! As you may know, an MVF column is not the same as a simple text column, so searching within an MVF would need special handling. I believe what you want to achieve is possible, but if you can avoid using MVFs, then your job would become easier. To help you with your current...

Sorry, No. The Value property is usually updated only once the focus leaves the control. PS. I don't use UserForms in Access. You might give it a try and maybe it behaves differently than regular forms.

Access has UserForms as well.

If you don't want to use a textbox, you could try using TempVars.