DeadShot
06-14-2017, 01:38 PM
We currently are migrating our access(vba) projects from access 2003(win xp) to access 2013(win 7).
Our db's are scheduled to run at various times. From the auto launch tool, command line variables are passed to the db's for the particular run.
There is no requirement for user's to pick the variables.
When i am running a access db, where in there is a call to a access query in the vba module. There is a error popping up
Error: undefined function command$ in expression......
In the query there is check in the where condition with the command line args passed i.e. Select ....From... where columnABC = command$()
This was working fine in access 2003. I am not able to find any resources for this issue.
If any further information is required let me know. Can anyone help me out.
Thanks
Our db's are scheduled to run at various times. From the auto launch tool, command line variables are passed to the db's for the particular run.
There is no requirement for user's to pick the variables.
When i am running a access db, where in there is a call to a access query in the vba module. There is a error popping up
Error: undefined function command$ in expression......
In the query there is check in the where condition with the command line args passed i.e. Select ....From... where columnABC = command$()
This was working fine in access 2003. I am not able to find any resources for this issue.
If any further information is required let me know. Can anyone help me out.
Thanks