ODBC connection thru DTS prompting for username/pw 1

[katinicsdad]

The version of Mas90 I have is version 3.71. I have a DTS importing the MAS90 tables into SQL SERVER Using the SOTAMAS90 ODBC connection. When I run my import it prompts me to enter the user name and password for each table. Is there any way to keep it from prompting? I want to automate my imports where no users are required. Any help will be greatly appreciated.

 

[Blorf]

The following works nicely with an access database, so I am thinking if you create with access, and create an odbc to the access database to let access read sotamas, it may work for you, or possibly you can do the same with your sql setup.

ChaZ

----------------------------------------

This is probably the most accessed information on the BestTalk forum and I thought I'd put it on here as well so we can have another place for it.

Thanks BigLouie for your contribution

Creating a pass through query in Access is really easy.
1. Open Crystal and start a new report
2. Base report on ONE MAS200 table
3. Pull into the detail section all fields you want
4. Go to Database on the menu
5. Go to Show SQL Statement
6. Highlight and copy the entire SQL statement.
7. Open your Access application
8. Go to Queries
9. Create New Query
10. Close tables box that opens.
11. Change Query type to SQL specific
12. When edit window opens paste in SQL statement from Crystal
13. Go to View on menu
14. Go to Properties
15. Click just to the right of the ODBC Connect St. box
16. Follow wizard to MAS200 and log in.
17. Select Save Password.
18. Edit the resulting ODBC connection string so that it looks like this:

 

[vtsmike]

If you run the DTS on the same machine each time, you can set up a SILENT ODBC connection.

On the machine, using the ODBC administration you can...

open the ODBC admin tool
ADD new USER DATA SOURCE
specify the SOTAMAS90 as the type
Give it a name like SOTAMAS90_SILENT
Provide the path the the database in database directory
fill in a company code, user name and password
check off dirty read and burst mode
cache can be 4MB

Then remap your ODBC connection to this new entry, and you should be all set.

 

[katinicsdad]

Worked perfectly! thanks vtsmike!