Hi All,
As you have seen from a previous post on this thread, I have been
STRUGGLING with the same issue for a long time. Here's Good News. I finally got the ASP Connection I wanted through ODBC.
BUT BEFORE WE GO ANY FURTHER I WOULD LIKE TO WARN YOU ALL.
Firstly this is not the best way to access certain data live, especially the detail files if they are huge since the ODBC engine seems to be scanning through the records sequentially.
Secondly You may have to open up file shares to the MAS90/200 Folder on your server where your ASP is. Now since I am doing this in a closed (Secured) intranet environment, it works fine for me, but it may create security issues which
you![[poke] [poke] [poke]](/data/assets/smilies/poke.gif)
need to take care of.
Thirdly don't expect much help from the MAS200 support or look for documentation, there is practically none. In fact I had a tough time even getting a decent reply when it came to ODBC. Not that Sage/BEST/MAS90 support is impolite or non-cooperative, its just this area (ODBC) which tends to bring out the
![[alien] [alien] [alien]](/data/assets/smilies/alien.gif)
Mr.Hyde
![[alien] [alien] [alien]](/data/assets/smilies/alien.gif)
in them.
Here's what we did to get this thing on the road:
Now what we did was download the PROVIDEX ODBC DRIVER from the providex website. MAS90 providex driver is no use. I think they have hacked it so that we cannot access the odbc thru asp.
![[tongue] [tongue] [tongue]](/data/assets/smilies/tongue.gif)
Providex is the generic driver which should work on any providex database (including Mas200). When you create a DSN on the IIS server, make sure to use the
Providex ODBC instead of the
MAS90 32 Bit ODBC and point it to the Network share which should be made available as a mapped drive (say M:\) on the IIS server.
Then the rest of the settings are no problems.
Try that and see if it works. But keep in mind the side effects.
Good Luck
![[thumbsup2] [thumbsup2] [thumbsup2]](/data/assets/smilies/thumbsup2.gif)
Kush.