FileMaker Pro and ASP

Sure.  Once you have created the system DSN, do this:

<%
Dim cn, rs, sql
Set cn = Server.CreatObject("ADODB.Connection")
sql = "SELECT Name FROM Users"
Set rs = cn.Execute(sql)
Do Until rs.EOF
     Response.Write rs("Name") & "<br>"
     rs.MoveNext
Loop
rs.Close
Set rs = Nothing
cn.Close
Set cn = Nothing
%>

Oops, should be this:

<%
Dim cn, rs, sql
Set cn = Server.CreatObject("ADODB.Connection")
cn.Open YourDSN
sql = "SELECT Name FROM Users"
Set rs = cn.Execute(sql)
Do Until rs.EOF
     Response.Write rs("Name") & "<br>"
     rs.MoveNext
Loop
rs.Close
Set rs = Nothing
cn.Close
Set cn = Nothing
%>

I'm not able to get either of these to work.  For the second one, I get ADODB.Recordset error '800a0e7d'
Operation is not allowed on an object referencing a closed or invalid connection.

On the first one, it wasn't recognizing the DSN.

What is,

   Set cn = Server.CreateObject("ADODB.Connection")
   Set rs = Server.CreateObject("New ADODB.Recordset")

   cn.Open "Provider=MSDASQL.1;Data Source=FMTest;database=Sample02.fp5"
   Response.Write cn.State

Which FM version? Which code, and the error line? Any comments on the procedure MS recommended in their article? - You need to feed your consultants :-)

I've been looking at connecting to Filemaker Pro databases with ASP lately.  In their literature I read that you can only have 10 seperate connections in a 12 hour period.  That's with FP 5.5 anyway.

Might be worth considering.

You can maintain one connection object with ASP and share it...

No comment has been added lately, so it's time to clean up this TA.
I will leave a recommendation in the Cleanup topic area that this question is:
Accept robbert's comment as answer.
Please leave any comments here within the next seven days.
 
PLEASE DO NOT ACCEPT THIS COMMENT AS AN ANSWER!
 
puranik_p
EE Cleanup Volunteer