> But I experience a couple of drawbacks with this way of working. Thanks to this generalization, I do not even have to bother about datatype syntax either in many cases. So, in my work towards generalization and re-use of code, I never use your proposed syntax, but I realize that this is a personal choice. In constructing SQL strings with the same logical selection you may not use this construction either. Further you must specify the full name of the control in this syntax:Īny generalization is not allowed, so you may not use form or control variables.ģ. and I do not want to distinguish between the two in how to pass an argument.Ģ. It works only for Access functions, and not for "home made" functions. You are quite right that one may use the Form control reference in an Access function.īut I experience a couple of drawbacks with this way of working.ġ. The advantage of NOT placing it outside the dbl-quotes is that the parameter will likely return a specific datatype,Īnd therefor there is no need to worry with delimiters.
That is NOT true, DLookup() can resolve parameters that refer to Form control references since it is an Access function. In order to use the VALUE of !ReportForm]!, you have to place it outside the doublequotes <<
0 kommentar(er)
