• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1850
  • Last Modified:

connecting MAS90 via ODBC in ACCESS 2000

Hello all,

I am having difficulties connecting to MAS90.  I have installed the server ProvideX drivers along with the local providex drivers.  ODBC is ALL new to me!  My goal is to have tables from MAS90 linked to my Access db.  The tables I want in particular are related to sales orders and product listings.  

Currently my company set up a test enviroment for me.  The network drive is \\m90test\m90\mas90\   For the life of me I have no clue what to use for the database directory.  It suggests that the directory should contain a file called PROVIDEX.DDF.  I do not have any directories that show that file.  For the definition file I am using
\\m90test\m90\mas90\home and for my views dll I am using \\m90test\m90\mas90\home also.

when i click "test connection" it says "connection succeeded, datasource includes [0] tables".

Obviously I am using this incorrectly and I would like some guidance.  Please help ASAP!!!

VIC
0
lightcross
Asked:
lightcross
  • 12
  • 11
  • 3
1 Solution
 
lightcrossAuthor Commented:
the link does not work.  can you please post it again?
0
What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

 
lightcrossAuthor Commented:
yeah...i know that link!  it doesnt help me.  
0
 
lightcrossAuthor Commented:
the problem is that i dont see "Mas90 32-bit ODBC Driver", I only have "ProvideX 32-bit ODBC Driver".  Is it the same difference?  I dont think so because its not working as suggested.
0
 
MourdekaiCommented:
Yes, the ProvideX 32-bit ODBC Driver is the one you want to use.  Mas90 uses the ProvideX driver.

You don't need to fill out the definition file, and use \\m90test\m90\mas90 for your database directory.
0
 
lightcrossAuthor Commented:
what about the database directory not containing the *.ddf file?  when i use test connection it says "connection succeeded, datasource includes [0] tables".
but it will also say that even if I dont fill in any information.  

am i supposed to be doing this in the access database itself?  im using "link tables" and choosing odbc databases.
0
 
lightcrossAuthor Commented:
ok!  I dont know what I did different but it is working now!  I was able to link the tables but i cant view the data within them.  if i run a test query just to see data i get an error "odbc call failed - [provideX][odbc driver][fileio] table is not accessible (#12)"  

why is this?

wow...its tricky to know which tables you need to access to get the data you need!
0
 
MourdekaiCommented:
If you have the Mas90 launcher installed on your computer, I believe it sets up an ODBC connection for you.  

When you click File -> Get External Data -> Link Tables, is there an entry for SOTAMAS90.dsn?  If there is, you can choose that and it will connect to mas90 and have you sign in and then you can select your tables.

Also, is Mas90 installed on the server in the location: \\m90test\m90\mas90 ?

And how are you trying to create your new data source?  Are you trying to do that in Access?  Or are you going to Control Panel -> Administrative Tools -> ODBC Sources ?
0
 
MourdekaiCommented:
Just saw your last post.  I'm not sure why you are getting that error.  And yes, it is hard to know which tables you need to link.  If you have the technical support resource guide that came on a cd with your mas90 install set, it is a pdf file that can help sift through what tables contain what.
0
 
lightcrossAuthor Commented:
When you click File -> Get External Data -> Link Tables, is there an entry for SOTAMAS90.dsn?  If there is, you can choose that and it will connect to mas90 and have you sign in and then you can select your tables.
                    no

Also, is Mas90 installed on the server in the location: \\m90test\m90\mas90 ?
                    yes

And how are you trying to create your new data source?  Are you trying to do that in Access?  Or are you going to Control Panel -> Administrative Tools -> ODBC Sources ?
                   i did it in control panel, but when i try to link tables it runs me through the same process as the control panel admin tools.  seems redundant??

THANKS FOR YOUR REPLY!  
0
 
lightcrossAuthor Commented:
I dont know if this is a stupid question but does the ODBC server have to be running on the server side for me to access tables via Access?
0
 
MourdekaiCommented:
I don't think this uses an ODBC server.  You connect through an ODBC driver that is installed on your local machine.

Also, are you trying to read the data or perform writes on the data, or both?
0
 
lightcrossAuthor Commented:
I only care about reading data.  we are trying to create a portion of the access database currently used in manufacturing to recognize when a sale is made and stuff like that.  
0
 
MourdekaiCommented:
The error you are getting:

odbc call failed - [provideX][odbc driver][fileio] table is not accessible (#12)

Can happen if your company has implemented ODBC Security through Library Master in Mas90, is this the case?
0
 
lightcrossAuthor Commented:
ok, they just changed the read to "1" for the SO (sales order module).  We are just testing so it doesnt really matter what im reading right now.  Anyway, I get the same error.  Should I re-link the tables after the changes in MAS90?  
0
 
MourdekaiCommented:
Try just closing the database and re-opening it.  If that doesn't work, delete the link, and re-create it.

Also what versions of:

Mas90
ProvideX Driver
Access
Windows

are you using?
0
 
MourdekaiCommented:
Lightcross, any luck?  What's your current status?
0
 
lightcrossAuthor Commented:
my current status is that I am able to connect and now view the data.  the only problem is that i have ODBC timeout errors.  am i only going to be able to create forms using queries haveing the timeout properties set to zero?  I will award you points by today if I have no more questions.  are you ok with that???
0
 
MourdekaiCommented:
I haven't received any timeout errors using links to mas90.  Do you receive the timeout errors when you set the property to zero?
0
 
lightcrossAuthor Commented:
not in queries but in openning tables up yes.
0
 
MourdekaiCommented:
What's the error message?  And does this happen right when you open up the table?  Or how long does it take?
0
 
lightcrossAuthor Commented:
its just some timeout error on some of the larger tables in mas.  i think it takes like 30-40 seconds.  i got the timeout error recently on a query that had odbc timeout set to "0".  strange!
0
 
MourdekaiCommented:
Maybe try changing some settings under the menu Tools->Options and then the advanced tab.  I'm not sure what setting to change though.  (Also, this is in Access 2002)
0
 
MourdekaiCommented:
Lightcross, if the tables are successfully linked, but you are getting timeout problems you might want to start another question for that so other experts can give their input.  I haven't received these errors linking to Mas90 so I am unsure of what to do.
0

Featured Post

Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

  • 12
  • 11
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now