I have an issue where a query in Access 2000 Runtime runs differently to Access 2000 (development).
In Access 2000, if a query has a parameter that has a function applied to it, the default order of events is: Access 2000 requests the parameter, then the function is applied to the parameter.
However, in Access 2000 Runtime, when the query is executed, the function is performed straight away i.e. when the parameter is null, and hence the function bombs with an error message (This I reckon is some sort of precompilation). Then the parameter is (at long last!!) requested and finally the function is applied again, this time successfully.
Has anyone else had experience of this Development/Runtime disrepancy? and how was it corrected?
TIA
M.
In Access 2000, if a query has a parameter that has a function applied to it, the default order of events is: Access 2000 requests the parameter, then the function is applied to the parameter.
However, in Access 2000 Runtime, when the query is executed, the function is performed straight away i.e. when the parameter is null, and hence the function bombs with an error message (This I reckon is some sort of precompilation). Then the parameter is (at long last!!) requested and finally the function is applied again, this time successfully.
Has anyone else had experience of this Development/Runtime disrepancy? and how was it corrected?
TIA
M.
