Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Problem with calling Customer job 1

Status
Not open for further replies.
Aug 15, 2007
29
PK
Hello all,

The problem that i am facing is that i made a Customer Export job and tested it manually.It is running fine.But when i tried to call this job by writing its credendials and its name in the shortcut of pvxwin32.com

"C:\Program Files\Sage Software\MAS 90\Version4\MAS90\Home\pvxwin32.exe" ..\LAUNCHER\SOTAPGM.INI ..\SOA\STARTUP.M4P -ARG DIRECT UION salman 123 ABC VIWX08 AUTO

then it is not executing however if change AUTO to Manual then its execution Window appears infront of me.
However,I have also made and called some other jobs of items,vendors but i don't found any problem in them but with customer it is creating problem.

Can you please tell me what is the problem with my job?

Waiting for ur response
Regards
 
Using VI to export is NOT the preferred way of doing this. I would suggest using Access or Excel to pull instead. Way faster.
 
Thanks for your responses,

For BigLouie:

Can you please help how to pull information from Access because according to my knowlege MAS90 4.10 donot has any data base .What driver will be used to pull information from access or Excel if i am using a .Net application.Is there any sample application available for this purpose.


For dfeller:

I have already tried using DISPLAY and MANUAL .
On display it doesnot show any thing.However on Manual it opens the Job's Window.
Now what do you think is the problem.

 
From the upcoming book Query This! here is how to create a SQL Specific Pass Through Query with Auto-Login

1. Start up Microsoft Access. The steps below will vary depending on version of Access and personal preferences. Click on File, New and choose Blank Database. Save the database on a local drive or in a location of your choice. Or open an existing Access database
2. Open Crystal and start a new report
3. Base report on ONE MAS200 table.
4. Pull into the detail section all fields you want.
5. Go to Database on the menu
6. Go to Show SQL Statement
7. Highlight and copy the entire SQL statement.
8. Go back to your Access application
9. Go to Queries
10. Create New Query
11. Close table box that opens.
12. Change Query type to SQL specific
13. When edit window opens paste in SQL statement from Crystal
14. Go to View on menu
15. Go to Properties
16. You will need to type in the connection string as follows because the ODBC connection Wizard in Access will not work with the MAS 4.0 ODBC driver in many cases:
ODBC;DSN=SOTAMAS90;UID=XXX|ABC;PWD=XYZ;Directory=\\account\account$\Best\MAS 200\Version4\MAS90\;SERVER=NotTheServer
17. Where XXX is the user ID, ABC is the company code and XYZ is the password. The rest will be based on your system. Note there is a | between the user ID and the company code.
18. A very very important note is on the ODBC connection string, make sure that DirtyReads=1 and BurstMode=1 is removed. It is critcial to omit these options in the connection string.
19. Save.
20. You now have a working pass-through query with auto-login. This method returns data faster than a linked table and allows you to connect to MAS without having to create a silent DSN.
 
Thanks, BL for the step-by-step. What if you need more than one table, though (i.e., ARN & ARO)?
 
You create a query for each table you need. Then you create either Make Table or Append queries to popular tables.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top