After splitting db, VBA having problems

[jobrien4]

I created a db mostly through VBA and have spent a few weeks testing and have never seen this error. I finally split the db, and distributed the front end.

Sometimes things work fine, but eventually the user gets the following error when clicking a command button or doing some other event:

"The expression On Click you entered as the event property setting produced the following error: You entered an expression that has no value"

I've only been able to see this error on one of the .accde files so I can't locate the error in the code. I'll try to recreate the error in the .accdb file, but does anyone have any ideas in the meantime?

 

[josephff]

i would guess that the value being returned from your code is null and there is nothing setup to handle the null value

 

[MSAccessRookie]

Without any additional information, it is dificult to do more than guess, but below are two descriptions of situations where the error occurs, as well as resolutions for those situations.


http://social.msdn.microsoft.com/forums/en-US/isvvba/thread/a193d494-3fd8-4e17-aa6a-4e918eff952a

http://bytes.com/topic/access/answers/723066-expression-no-value

 

[MSAccessRookie]

i would guess that the value being returned from your code is null and there is nothing setup to handle the null value

Don't forget that when you are dealing with VBA, another issue to consider is that any variable that has been declared but not yet defined has a value of NOTHING, not NULL, so you might need to test for NOTHING as well

 

[jobrien4]

I think the error stemmed from a Yes/No field I had where I had no default value and a Dlookup set a boolean as the value of the field.

I changed all the defaults on the Yes/No's to False so hopefully that takes care of that.

I think the error through me off because I never saw it before, because it was in .accde. I've done all the debugging in .accdb where it takes you straight to the error in the code