[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [cobalt-users] ODBC driver for MS-Access under ASP?



> Has anyone found an ODBC driver for MS-Access under ASP on a Cobalt?

Hi Edwin,

You will need to host your MS Access database on a Windows based machine, as
Microsoft don't support any method (to my knowledge) of running Access on a
Linux or Unix based OS.

Fortunately, the clever guys at Cobalt / Chili!Soft have provided a way of
linking your RaQ up to an external machine just for these purposes :-)

These instructions are based on RaQ4... and the database will need to be
Access 98 or lower. AFAIK Access 2000 isn't supported through this method.

SETTING UP DATABASE HOST:
1. Set yourself up a Windows NT machine on a network accessible from your
RaQ.
2. Create an NT user (with basic privileges to log on to the machine).
2. Copy your Access database onto this machine.
3. Install the SequeLink server (I'm DAMNED if I can remember where I
downloaded this from - it's freely available from SOMEWHERE though. You
might want to email support@xxxxxxxxxxxxx as they should be able to help,
and advise you on what username to register it with for free and continued
use).

SETTING UP RAQ:
1. Telnet into your machine.
2. Type "su -" to give yourself the required access level.
3. Move to the /home/chiliasp/asp-apache-3000/ folder.
4. Type "./setsqlnk" to start up the admin tool.
5. Hit "2" to create a New data source.
6. Give it a name (remember this!!).
7. Give it a description (optional).
8. Hit <ENTER> on transliteration - DON'T type anything!
9. Select "1" for TCP/IP network.
10. Type the database host IP address.
11. Select "4" for Windows NT server type.
12. Type in your NT username (created earlier).
13. Type in the NT password.
14. Choose "12" for the database type (ODBC MS Access).
15. Type "SLSocket" as the name of the socket.
16. Type the FULL PATH to your database (e.g. c:\databases\dbase.mdb).
17. Now test the connection using "6". You should get a message saying "Test
passed: connection to 'dsnName' made."

If the test FAILS - check that your NT user is created correctly and that
they have the ability to log on locally to the machine. Make sure their
password is correct and also it might be worth making sure the password
NEVER expires. Double-check your path to the database in SequeLink and
ensure that the IP address etc are correct.

SETTTING UP IN GUI:
1. Log in to the GUI as admin.
2. Go to the Control Panel.
3. Log into the ASP Admin Server.
4. Go to "Database Settings".
5. Select "Add new DSN".
6. Select "SequeLink" as the driver.
7. Enter a name for the DSN.
8. Enter a description (optional).
9. Type in the SQLnkDSN EXACTLY as you typed the name in step 6 previously.
10. Click Next and then Finish to create the DSN
11. Use "Test" to check the connection is working correctly.

If the test FAILS - check that your SQLnkDSN name is the same as the name
you gave it in setsqlnk. Also make sure that the IP / hostname you are
logged into has ASP enabled in the Server Management section. Make sure you
HAVEN'T filled in any extra settings anywhere such as database path etc.

You should now be able to use the DSN in your ASP code!! PHEW. I'm done
typing now...

Good luck!

        -Richard Abrams