Hello myDBR representative,
How are you doing? I just noticed that since our upgrade to myDBR version 4.3.3 over this weekend we have had one particular report started passing "0" instead of NULL for empty integer typed parameters. I checked out report logs and it does not look like the report procedure, parameters, or defaults were changed. I'm not sure what, other than the update, might have caused the change in the handling of non-populated integer typed parameters. Any assistance is appreciated!