lindar
12th March 2009, 23:40
I'm not sure what I am missing. I run several jobs with startjob and they all run as setup. I am now trying to set up a sql job to runs at night and my problem is the query when using Ctrl G sets up a job session in company 000 not in the company I am working in. I have tried running the query in company 000 and I get the errror "object of report not found in your package"
Any help appreciated.
Hitesh Shah
13th March 2009, 17:27
Though one can not add ._compnr directly in easy sql , U can try writing ._compnr in sql text and then run the job .
Not sure if ._compnr existed in 3.1b or not . Test it out .
lindar
13th March 2009, 20:54
how will setting company number in query help?
lindar
13th March 2009, 23:28
I did find a work around. I just hand typed the information into the ttadv500,501 and 503 files and it kicked off fine. Now if it just runs Monday I will be all set. Still would like an easier way. If any suggestions.
Hitesh Shah
17th March 2009, 06:21
I did find a work around. I just hand typed the information into the ttadv500,501 and 503 files and it kicked off fine. Now if it just runs Monday I will be all set. Still would like an easier way. If any suggestions.
I suppose u mean ttaad tables and not ttadv tables. CTRL + G is the front end to enter data in the tables u described .
The report object u may have created may be in a vrc not in ur package combination of the company u run job in.
lindar
18th March 2009, 00:16
Sorry I did mean the ttaad tables, and yes something seems to be wrong with the way the query setsup. When I use a "G" at choice the job sets up in Company 000 and when activated I receive the error object not in VRC, even though I am in company 250 (our company number)
When I activate the job today it will run, (after I hand inputed the file information). But tonight the system will shutdown and restart in the morning, the job will not activate tommorrow. I will get a runtime error in the jobdata file.
All help appreciated