Could not find installable ISAM

[Serge Myrand]

Hi,

Using this ASP code I get the error Could not find installable ISAM. I
always connect to Access databases using ADO and Delphi. I never got
this error message. I want to use ADO within ASP code what is the
problem I have? I tried with Access db 97, 2000 and 2002, always the
same message. Any help will be appreciate.

<%@ Language=VBScript %>
<% option explicit %>
<% Response.Buffer=True %>
<%
dim conn
Set conn = Server.CreateObject("ADODB.Connection")
conn.ConnectionString="Provider=Microsoft.Jet.OLED B.4.0;DataSource=" &
_
Server.MapPath("Test.mdb")
conn.CursorLocation=adUseClient
conn.Mode= adModeRead
conn.Open
%>

thank's in advance
serge

[Aaron [SQL Server MVP]]

Are you sure you have Jet 4.0 installed?

[url]http://www.aspfaq.com/2342[/url]

--
[url]http://www.aspfaq.com/[/url]
(Reverse address to reply.)




"Serge Myrand" <info@softdelirium.qc.ca> wrote in message
news:40C76878.45F26779@softdelirium.qc.ca...

> Hi,
>
> Using this ASP code I get the error Could not find installable ISAM. I
> always connect to Access databases using ADO and Delphi. I never got
> this error message. I want to use ADO within ASP code what is the
> problem I have? I tried with Access db 97, 2000 and 2002, always the
> same message. Any help will be appreciate.
>
> <%@ Language=VBScript %>
> <% option explicit %>
> <% Response.Buffer=True %>
> <%
> dim conn
> Set conn = Server.CreateObject("ADODB.Connection")
> conn.ConnectionString="Provider=Microsoft.Jet.OLED B.4.0;DataSource=" &
> _
> Server.MapPath("Test.mdb")
> conn.CursorLocation=adUseClient
> conn.Mode= adModeRead
> conn.Open
> %>
>
> thank's in advance
> serge
>

[Serge Myrand]

Hi,

Yes I am. I use it every single day in Delphi. Except error, ISAM worth for
Jet 2x and Jet 3x. Any oyher idea?

thank you
serge


"Aaron [SQL Server MVP]" wrote:

> Are you sure you have Jet 4.0 installed?
>
> [url]http://www.aspfaq.com/2342[/url]
>
> --
> [url]http://www.aspfaq.com/[/url]
> (Reverse address to reply.)
>
> "Serge Myrand" <info@softdelirium.qc.ca> wrote in message
> news:40C76878.45F26779@softdelirium.qc.ca...

> > Hi,
> >
> > Using this ASP code I get the error Could not find installable ISAM. I
> > always connect to Access databases using ADO and Delphi. I never got
> > this error message. I want to use ADO within ASP code what is the
> > problem I have? I tried with Access db 97, 2000 and 2002, always the
> > same message. Any help will be appreciate.
> >
> > <%@ Language=VBScript %>
> > <% option explicit %>
> > <% Response.Buffer=True %>
> > <%
> > dim conn
> > Set conn = Server.CreateObject("ADODB.Connection")
> > conn.ConnectionString="Provider=Microsoft.Jet.OLED B.4.0;DataSource=" &
> > _
> > Server.MapPath("Test.mdb")
> > conn.CursorLocation=adUseClient
> > conn.Mode= adModeRead
> > conn.Open
> > %>
> >
> > thank's in advance
> > serge
> >

[Bob Barrows [MVP]]

I suggest you download and install the latest Jet service pack from MS.

Bob Barrows
Serge Myrand wrote:

> Hi,
>
> Yes I am. I use it every single day in Delphi. Except error, ISAM
> worth for Jet 2x and Jet 3x. Any oyher idea?
>
> thank you
> serge
>
>
> "Aaron [SQL Server MVP]" wrote:
>

>> Are you sure you have Jet 4.0 installed?
>>
>> [url]http://www.aspfaq.com/2342[/url]
>>
>> --
>> [url]http://www.aspfaq.com/[/url]
>> (Reverse address to reply.)
>>
>> "Serge Myrand" <info@softdelirium.qc.ca> wrote in message
>> news:40C76878.45F26779@softdelirium.qc.ca...

>>> Hi,
>>>
>>> Using this ASP code I get the error Could not find installable
>>> ISAM. I always connect to Access databases using ADO and Delphi. I
>>> never got this error message. I want to use ADO within ASP code
>>> what is the problem I have? I tried with Access db 97, 2000 and
>>> 2002, always the same message. Any help will be appreciate.
>>>
>>> <%@ Language=VBScript %>
>>> <% option explicit %>
>>> <% Response.Buffer=True %>
>>> <%
>>> dim conn
>>> Set conn = Server.CreateObject("ADODB.Connection")
>>> conn.ConnectionString="Provider=Microsoft.Jet.OLED B.4.0;DataSource="
>>> & _
>>> Server.MapPath("Test.mdb")
>>> conn.CursorLocation=adUseClient
>>> conn.Mode= adModeRead
>>> conn.Open
>>> %>
>>>
>>> thank's in advance
>>> serge

--
Microsoft MVP -- ASP/ASP.NET
Please reply to the newsgroup. The email account listed in my From
header is my spam trap, so I don't check it very often. You will get a
quicker response by posting to the newsgroup.

[Serge Myrand]

(Bob, excuse me for answering to your personnal address, it's a mistake, I am
sorry)

Hi,

I have just re-installed MDAC 2.7 SP1 and JetOLEDB 4.0 SP8. I still have the

same problem. I tried my ASP file on XP pro and Win 2000 Pro. With the same
result, an error message: Could not find installable ISAM.

I really do not know what to do next!

any idea?
thank's
serge

"Bob Barrows [MVP]" wrote:

> I suggest you download and install the latest Jet service pack from MS.
>
> Bob Barrows
> Serge Myrand wrote:

> > Hi,
> >
> > Yes I am. I use it every single day in Delphi. Except error, ISAM
> > worth for Jet 2x and Jet 3x. Any oyher idea?
> >
> > thank you
> > serge
> >
> >
> > "Aaron [SQL Server MVP]" wrote:
> >

> >> Are you sure you have Jet 4.0 installed?
> >>
> >> [url]http://www.aspfaq.com/2342[/url]
> >>
> >> --
> >> [url]http://www.aspfaq.com/[/url]
> >> (Reverse address to reply.)
> >>
> >> "Serge Myrand" <info@softdelirium.qc.ca> wrote in message
> >> news:40C76878.45F26779@softdelirium.qc.ca...
> >>> Hi,
> >>>
> >>> Using this ASP code I get the error Could not find installable
> >>> ISAM. I always connect to Access databases using ADO and Delphi. I
> >>> never got this error message. I want to use ADO within ASP code
> >>> what is the problem I have? I tried with Access db 97, 2000 and
> >>> 2002, always the same message. Any help will be appreciate.
> >>>
> >>> <%@ Language=VBScript %>
> >>> <% option explicit %>
> >>> <% Response.Buffer=True %>
> >>> <%
> >>> dim conn
> >>> Set conn = Server.CreateObject("ADODB.Connection")
> >>> conn.ConnectionString="Provider=Microsoft.Jet.OLED B.4.0;DataSource="
> >>> & _
> >>> Server.MapPath("Test.mdb")
> >>> conn.CursorLocation=adUseClient
> >>> conn.Mode= adModeRead
> >>> conn.Open
> >>> %>
> >>>
> >>> thank's in advance
> >>> serge

>
> --
> Microsoft MVP -- ASP/ASP.NET
> Please reply to the newsgroup. The email account listed in my From
> header is my spam trap, so I don't check it very often. You will get a
> quicker response by posting to the newsgroup.

[Bob Barrows [MVP]]

It's possibly a permissions issue. Try creating a udl file to test your
ability to connect to your database:

1. On the machine giving you the problem, create an empty text file
2. Change its extension to .udl
3. open it up - you should get a wizard to help you create a connection
4. follow the steps to choose the Jet OLEDB provider, point it at a db, etc
5. Test the connection

If the UDL file works correctly, close it then open it in Notepad to see the
connection string it generated. In your asp page, do this before attempting
to open the connection:

response.write conn.connectionstring
response.end

run the page and compare the connection strings.

Bob Barrows


Serge Myrand wrote:

> (Bob, excuse me for answering to your personnal address, it's a
> mistake, I am sorry)
>
> Hi,
>
> I have just re-installed MDAC 2.7 SP1 and JetOLEDB 4.0 SP8. I still
> have the
>
> same problem. I tried my ASP file on XP pro and Win 2000 Pro. With
> the same result, an error message: Could not find installable ISAM.
>
> I really do not know what to do next!
>
> any idea?
> thank's
> serge
>
> "Bob Barrows [MVP]" wrote:
>

>> I suggest you download and install the latest Jet service pack from
>> MS.
>>
>> Bob Barrows
>> Serge Myrand wrote:

>>> Hi,
>>>
>>> Yes I am. I use it every single day in Delphi. Except error, ISAM
>>> worth for Jet 2x and Jet 3x. Any oyher idea?
>>>
>>> thank you
>>> serge
>>>
>>>
>>> "Aaron [SQL Server MVP]" wrote:
>>>
>>>> Are you sure you have Jet 4.0 installed?
>>>>
>>>> [url]http://www.aspfaq.com/2342[/url]
>>>>
>>>> --
>>>> [url]http://www.aspfaq.com/[/url]
>>>> (Reverse address to reply.)
>>>>
>>>> "Serge Myrand" <info@softdelirium.qc.ca> wrote in message
>>>> news:40C76878.45F26779@softdelirium.qc.ca...
>>>>> Hi,
>>>>>
>>>>> Using this ASP code I get the error Could not find installable
>>>>> ISAM. I always connect to Access databases using ADO and Delphi. I
>>>>> never got this error message. I want to use ADO within ASP code
>>>>> what is the problem I have? I tried with Access db 97, 2000 and
>>>>> 2002, always the same message. Any help will be appreciate.
>>>>>
>>>>> <%@ Language=VBScript %>
>>>>> <% option explicit %>
>>>>> <% Response.Buffer=True %>
>>>>> <%
>>>>> dim conn
>>>>> Set conn = Server.CreateObject("ADODB.Connection")
>>>>> conn.ConnectionString="Provider=Microsoft.Jet.OLED B.4.0;DataSource="
>>>>> & _
>>>>> Server.MapPath("Test.mdb")
>>>>> conn.CursorLocation=adUseClient
>>>>> conn.Mode= adModeRead
>>>>> conn.Open
>>>>> %>
>>>>>
>>>>> thank's in advance
>>>>> serge

>>
>> --
>> Microsoft MVP -- ASP/ASP.NET
>> Please reply to the newsgroup. The email account listed in my From
>> header is my spam trap, so I don't check it very often. You will get
>> a quicker response by posting to the newsgroup.

--
Microsoft MVP -- ASP/ASP.NET
Please reply to the newsgroup. The email account listed in my From
header is my spam trap, so I don't check it very often. You will get a
quicker response by posting to the newsgroup.

[Serge Myrand]

Hi,

It was a good idea, it resolve my problem. The missing part was "Persist
Security Info=False". I ask to myself why do I need that? I never seen it in any
example before! It works even if I set it to "Persist Security Info=True" but it
does not work if I removed it...!

Thank you very much for your time
Serge

"Bob Barrows [MVP]" wrote:

> It's possibly a permissions issue. Try creating a udl file to test your
> ability to connect to your database:
>
> 1. On the machine giving you the problem, create an empty text file
> 2. Change its extension to .udl
> 3. open it up - you should get a wizard to help you create a connection
> 4. follow the steps to choose the Jet OLEDB provider, point it at a db, etc
> 5. Test the connection
>
> If the UDL file works correctly, close it then open it in Notepad to see the
> connection string it generated. In your asp page, do this before attempting
> to open the connection:
>
> response.write conn.connectionstring
> response.end
>
> run the page and compare the connection strings.
>
> Bob Barrows
>
> Serge Myrand wrote:

> > (Bob, excuse me for answering to your personnal address, it's a
> > mistake, I am sorry)
> >
> > Hi,
> >
> > I have just re-installed MDAC 2.7 SP1 and JetOLEDB 4.0 SP8. I still
> > have the
> >
> > same problem. I tried my ASP file on XP pro and Win 2000 Pro. With
> > the same result, an error message: Could not find installable ISAM.
> >
> > I really do not know what to do next!
> >
> > any idea?
> > thank's
> > serge
> >
> > "Bob Barrows [MVP]" wrote:
> >

> >> I suggest you download and install the latest Jet service pack from
> >> MS.
> >>
> >> Bob Barrows
> >> Serge Myrand wrote:
> >>> Hi,
> >>>
> >>> Yes I am. I use it every single day in Delphi. Except error, ISAM
> >>> worth for Jet 2x and Jet 3x. Any oyher idea?
> >>>
> >>> thank you
> >>> serge
> >>>
> >>>
> >>> "Aaron [SQL Server MVP]" wrote:
> >>>
> >>>> Are you sure you have Jet 4.0 installed?
> >>>>
> >>>> [url]http://www.aspfaq.com/2342[/url]
> >>>>
> >>>> --
> >>>> [url]http://www.aspfaq.com/[/url]
> >>>> (Reverse address to reply.)
> >>>>
> >>>> "Serge Myrand" <info@softdelirium.qc.ca> wrote in message
> >>>> news:40C76878.45F26779@softdelirium.qc.ca...
> >>>>> Hi,
> >>>>>
> >>>>> Using this ASP code I get the error Could not find installable
> >>>>> ISAM. I always connect to Access databases using ADO and Delphi. I
> >>>>> never got this error message. I want to use ADO within ASP code
> >>>>> what is the problem I have? I tried with Access db 97, 2000 and
> >>>>> 2002, always the same message. Any help will be appreciate.
> >>>>>
> >>>>> <%@ Language=VBScript %>
> >>>>> <% option explicit %>
> >>>>> <% Response.Buffer=True %>
> >>>>> <%
> >>>>> dim conn
> >>>>> Set conn = Server.CreateObject("ADODB.Connection")
> >>>>> conn.ConnectionString="Provider=Microsoft.Jet.OLED B.4.0;DataSource="
> >>>>> & _
> >>>>> Server.MapPath("Test.mdb")
> >>>>> conn.CursorLocation=adUseClient
> >>>>> conn.Mode= adModeRead
> >>>>> conn.Open
> >>>>> %>
> >>>>>
> >>>>> thank's in advance
> >>>>> serge
> >>
> >> --
> >> Microsoft MVP -- ASP/ASP.NET
> >> Please reply to the newsgroup. The email account listed in my From
> >> header is my spam trap, so I don't check it very often. You will get
> >> a quicker response by posting to the newsgroup.

>
> --
> Microsoft MVP -- ASP/ASP.NET
> Please reply to the newsgroup. The email account listed in my From
> header is my spam trap, so I don't check it very often. You will get a
> quicker response by posting to the newsgroup.

[Bob Barrows [MVP]]

That IS strange. I've never used that setting.

Bob Barrows
Serge Myrand wrote:

> Hi,
>
> It was a good idea, it resolve my problem. The missing part was
> "Persist Security Info=False". I ask to myself why do I need that? I
> never seen it in any example before! It works even if I set it to
> "Persist Security Info=True" but it does not work if I removed it...!
>
> Thank you very much for your time
> Serge
>
> "Bob Barrows [MVP]" wrote:
>

>> It's possibly a permissions issue. Try creating a udl file to test
>> your ability to connect to your database:
>>
>> 1. On the machine giving you the problem, create an empty text file
>> 2. Change its extension to .udl
>> 3. open it up - you should get a wizard to help you create a
>> connection
>> 4. follow the steps to choose the Jet OLEDB provider, point it at a
>> db, etc
>> 5. Test the connection
>>
>> If the UDL file works correctly, close it then open it in Notepad to
>> see the connection string it generated. In your asp page, do this
>> before attempting to open the connection:
>>
>> response.write conn.connectionstring
>> response.end
>>
>> run the page and compare the connection strings.
>>
>> Bob Barrows
>>
>> Serge Myrand wrote:

>>> (Bob, excuse me for answering to your personnal address, it's a
>>> mistake, I am sorry)
>>>
>>> Hi,
>>>
>>> I have just re-installed MDAC 2.7 SP1 and JetOLEDB 4.0 SP8. I still
>>> have the
>>>
>>> same problem. I tried my ASP file on XP pro and Win 2000 Pro. With
>>> the same result, an error message: Could not find installable ISAM.
>>>
>>> I really do not know what to do next!
>>>
>>> any idea?
>>> thank's
>>> serge
>>>
>>> "Bob Barrows [MVP]" wrote:
>>>
>>>> I suggest you download and install the latest Jet service pack from
>>>> MS.
>>>>
>>>> Bob Barrows
>>>> Serge Myrand wrote:
>>>>> Hi,
>>>>>
>>>>> Yes I am. I use it every single day in Delphi. Except error, ISAM
>>>>> worth for Jet 2x and Jet 3x. Any oyher idea?
>>>>>
>>>>> thank you
>>>>> serge
>>>>>
>>>>>
>>>>> "Aaron [SQL Server MVP]" wrote:
>>>>>
>>>>>> Are you sure you have Jet 4.0 installed?
>>>>>>
>>>>>> [url]http://www.aspfaq.com/2342[/url]
>>>>>>
>>>>>> --
>>>>>> [url]http://www.aspfaq.com/[/url]
>>>>>> (Reverse address to reply.)
>>>>>>
>>>>>> "Serge Myrand" <info@softdelirium.qc.ca> wrote in message
>>>>>> news:40C76878.45F26779@softdelirium.qc.ca...
>>>>>>> Hi,
>>>>>>>
>>>>>>> Using this ASP code I get the error Could not find installable
>>>>>>> ISAM. I always connect to Access databases using ADO and
>>>>>>> Delphi. I never got this error message. I want to use ADO
>>>>>>> within ASP code
>>>>>>> what is the problem I have? I tried with Access db 97, 2000 and
>>>>>>> 2002, always the same message. Any help will be appreciate.
>>>>>>>
>>>>>>> <%@ Language=VBScript %>
>>>>>>> <% option explicit %>
>>>>>>> <% Response.Buffer=True %>
>>>>>>> <%
>>>>>>> dim conn
>>>>>>> Set conn = Server.CreateObject("ADODB.Connection")
>>>>>>>

conn.ConnectionString="Provider=Microsoft.Jet.OLED B.4.0;DataSource="

>>>>>>> & _
>>>>>>> Server.MapPath("Test.mdb")
>>>>>>> conn.CursorLocation=adUseClient
>>>>>>> conn.Mode= adModeRead
>>>>>>> conn.Open
>>>>>>> %>
>>>>>>>
>>>>>>> thank's in advance
>>>>>>> serge
>>>>
>>>> --
>>>> Microsoft MVP -- ASP/ASP.NET
>>>> Please reply to the newsgroup. The email account listed in my From
>>>> header is my spam trap, so I don't check it very often. You will
>>>> get
>>>> a quicker response by posting to the newsgroup.

>>
>> --
>> Microsoft MVP -- ASP/ASP.NET
>> Please reply to the newsgroup. The email account listed in my From
>> header is my spam trap, so I don't check it very often. You will get
>> a quicker response by posting to the newsgroup.

--
Microsoft MVP -- ASP/ASP.NET
Please reply to the newsgroup. The email account listed in my From
header is my spam trap, so I don't check it very often. You will get a
quicker response by posting to the newsgroup.

[Jason James]

Hi all,

I am creating an ASP web service and wish to connect
to an MS Access 2003 database. However, when I
attempt to access the database I get the following
error

"Could not find installable ISAM"

I found this on a Microsoft web site.

"Although you cannot link a database object to either
Microsoft Internet Information Services (.htx, .idc) or
Microsoft Active Server Pages (.asp) output formats,
you can export (export: To output data and database
objects to another database, spreadsheet, or file
format so another database or program can use the
data or database objects. You can export data to a
variety of supported databases, programs, and file
formats.) the object to the desired output format and
then attach the file in a mail program, such as
Microsoft Office Outlook 2003. "

Is it true? Do I have to use SQL server for my webservices?

If I can use MS Access 2003 database files, how do
I connect to them?

Thanks,

Jason.

[Scott M.]

You do not *have* to use SQL Server, you *can* use Access and your problem
is not related to this. Your problem is either your connection string is
wrong or the target machine does not have the necessary MDAC components.

The correct connection string should be
"Provider=Microsoft.JET.OLEDB.4.0;Data Source=DatabasePhyscialPath"

Having said that, Access is not meant for multi-user environments (although
it can handle a limited amount of them). You may want to consider using
MSDE with an Access front-end.


"Jason James" <jason@dive-master.org> wrote in message
news:425f7e13.8705868@news.demon.co.uk...

> Hi all,
>
> I am creating an ASP web service and wish to connect
> to an MS Access 2003 database. However, when I
> attempt to access the database I get the following
> error
>
> "Could not find installable ISAM"
>
> I found this on a Microsoft web site.
>
> "Although you cannot link a database object to either
> Microsoft Internet Information Services (.htx, .idc) or
> Microsoft Active Server Pages (.asp) output formats,
> you can export (export: To output data and database
> objects to another database, spreadsheet, or file
> format so another database or program can use the
> data or database objects. You can export data to a
> variety of supported databases, programs, and file
> formats.) the object to the desired output format and
> then attach the file in a mail program, such as
> Microsoft Office Outlook 2003. "
>
> Is it true? Do I have to use SQL server for my webservices?
>
> If I can use MS Access 2003 database files, how do
> I connect to them?
>
> Thanks,
>
> Jason.

[Jason James]

Thanks Scott.

When I port the ocde I wrote for the WS and place it into a
winform app, everything works great.

I am therefore happy that the connection string is good and
I have the necessary MDAC files installed.

When I port the solution to SQL it all works just fine!!

Any other thoughts?

Thanks,

Jason

On Fri, 15 Apr 2005 11:02:17 -0400, "Scott M." <s-mar@nospam.nospam>
wrote:

>You do not *have* to use SQL Server, you *can* use Access and your problem
>is not related to this. Your problem is either your connection string is
>wrong or the target machine does not have the necessary MDAC components.
>
>The correct connection string should be
>"Provider=Microsoft.JET.OLEDB.4.0;Data Source=DatabasePhyscialPath"
>
>Having said that, Access is not meant for multi-user environments (although
>it can handle a limited amount of them). You may want to consider using
>MSDE with an Access front-end.
>
>
>"Jason James" <jason@dive-master.org> wrote in message
>news:425f7e13.8705868@news.demon.co.uk...

>> Hi all,
>>
>> I am creating an ASP web service and wish to connect
>> to an MS Access 2003 database. However, when I
>> attempt to access the database I get the following
>> error
>>
>> "Could not find installable ISAM"
>>
>> I found this on a Microsoft web site.
>>
>> "Although you cannot link a database object to either
>> Microsoft Internet Information Services (.htx, .idc) or
>> Microsoft Active Server Pages (.asp) output formats,
>> you can export (export: To output data and database
>> objects to another database, spreadsheet, or file
>> format so another database or program can use the
>> data or database objects. You can export data to a
>> variety of supported databases, programs, and file
>> formats.) the object to the desired output format and
>> then attach the file in a mail program, such as
>> Microsoft Office Outlook 2003. "
>>
>> Is it true? Do I have to use SQL server for my webservices?
>>
>> If I can use MS Access 2003 database files, how do
>> I connect to them?
>>
>> Thanks,
>>
>> Jason.

>
>

[Scott M.]

When you try this application as a web service, is it running on the same
machine as when you run it as a web form?

Has the folder containing the database AS WELL AS the database itself given
permission to the ASPNET user account for full access?

Are you sure that the database is in a virtual directory of IIS so that when
the web service tries to find it, it can? Are you also sure that the path
is specified correctly for IIS?


"Jason James" <jason@dive-master.org> wrote in message
news:425fdd19.13225567@news.demon.co.uk...

> Thanks Scott.
>
> When I port the ocde I wrote for the WS and place it into a
> winform app, everything works great.
>
> I am therefore happy that the connection string is good and
> I have the necessary MDAC files installed.
>
> When I port the solution to SQL it all works just fine!!
>
> Any other thoughts?
>
> Thanks,
>
> Jason
>
> On Fri, 15 Apr 2005 11:02:17 -0400, "Scott M." <s-mar@nospam.nospam>
> wrote:
>

>>You do not *have* to use SQL Server, you *can* use Access and your problem
>>is not related to this. Your problem is either your connection string is
>>wrong or the target machine does not have the necessary MDAC components.
>>
>>The correct connection string should be
>>"Provider=Microsoft.JET.OLEDB.4.0;Data Source=DatabasePhyscialPath"
>>
>>Having said that, Access is not meant for multi-user environments
>>(although
>>it can handle a limited amount of them). You may want to consider using
>>MSDE with an Access front-end.
>>
>>
>>"Jason James" <jason@dive-master.org> wrote in message
>>news:425f7e13.8705868@news.demon.co.uk...

>>> Hi all,
>>>
>>> I am creating an ASP web service and wish to connect
>>> to an MS Access 2003 database. However, when I
>>> attempt to access the database I get the following
>>> error
>>>
>>> "Could not find installable ISAM"
>>>
>>> I found this on a Microsoft web site.
>>>
>>> "Although you cannot link a database object to either
>>> Microsoft Internet Information Services (.htx, .idc) or
>>> Microsoft Active Server Pages (.asp) output formats,
>>> you can export (export: To output data and database
>>> objects to another database, spreadsheet, or file
>>> format so another database or program can use the
>>> data or database objects. You can export data to a
>>> variety of supported databases, programs, and file
>>> formats.) the object to the desired output format and
>>> then attach the file in a mail program, such as
>>> Microsoft Office Outlook 2003. "
>>>
>>> Is it true? Do I have to use SQL server for my webservices?
>>>
>>> If I can use MS Access 2003 database files, how do
>>> I connect to them?
>>>
>>> Thanks,
>>>
>>> Jason.

>>
>>

>

[Jason James]

Scott,
I tried it again on a different machine running VS.Net and
MS WIndows 2K and MS Office 2K (not 2003). Gave ASPNET
read and write to the DB file only (not the folder), it is
contained in a folder that is not a virtual directory, and
everything worked just fine. I am going to try again on my
other machine (running XP and MS Office 2003) and see what
happens. If ther are no known issues with MS Office 2003
and Windows XP then I must have done something stupid.
I'll let you know in a while.

Many thanks for sticking with me on this.

Jason.


*** Sent via Developersdex [url]http://www.developersdex.com[/url] ***

[Scott M.]

Ok, good luck. FYI - you do not need to have Office (or Access) installed
on the machine with the database housed on it, that's what MDAC is for.


"Jason James" <jason.nospam@dive--master_nospam.org> wrote in message
news:OOTTDQeQFHA.2972@TK2MSFTNGP14.phx.gbl...

>
> Scott,
> I tried it again on a different machine running VS.Net and
> MS WIndows 2K and MS Office 2K (not 2003). Gave ASPNET
> read and write to the DB file only (not the folder), it is
> contained in a folder that is not a virtual directory, and
> everything worked just fine. I am going to try again on my
> other machine (running XP and MS Office 2003) and see what
> happens. If ther are no known issues with MS Office 2003
> and Windows XP then I must have done something stupid.
> I'll let you know in a while.
>
> Many thanks for sticking with me on this.
>
> Jason.
>
>
> *** Sent via Developersdex [url]http://www.developersdex.com[/url] ***

[Amil]

I just had this last night as well. Turned out to be the connection string;
you MUST be very careful for exact format using using "JET OLEDB:..."
elements. In my case, it was a space after the : character :-(

Amil

"Scott M." <s-mar@nospam.nospam> wrote in message
news:#d#A3weQFHA.3456@TK2MSFTNGP10.phx.gbl...

> Ok, good luck. FYI - you do not need to have Office (or Access) installed
> on the machine with the database housed on it, that's what MDAC is for.
>
>
> "Jason James" <jason.nospam@dive--master_nospam.org> wrote in message
> news:OOTTDQeQFHA.2972@TK2MSFTNGP14.phx.gbl...

> >
> > Scott,
> > I tried it again on a different machine running VS.Net and
> > MS WIndows 2K and MS Office 2K (not 2003). Gave ASPNET
> > read and write to the DB file only (not the folder), it is
> > contained in a folder that is not a virtual directory, and
> > everything worked just fine. I am going to try again on my
> > other machine (running XP and MS Office 2003) and see what
> > happens. If ther are no known issues with MS Office 2003
> > and Windows XP then I must have done something stupid.
> > I'll let you know in a while.
> >
> > Many thanks for sticking with me on this.
> >
> > Jason.
> >
> >
> > *** Sent via Developersdex [url]http://www.developersdex.com[/url] ***

>
>

[Scott M.]

Yep. What "could not find installable ISAM" means is that the compiler
couldn't find the provider specified in the connection string. There are
only 2 reasons it would say that: either the provider is correct, but not
installed on the machine or the connection string is incorrect.


"Amil" <AmilHanish@hotmail.com> wrote in message
news:%23WBn9KFRFHA.204@TK2MSFTNGP15.phx.gbl...

>I just had this last night as well. Turned out to be the connection
>string;
> you MUST be very careful for exact format using using "JET OLEDB:..."
> elements. In my case, it was a space after the : character :-(
>
> Amil
>
> "Scott M." <s-mar@nospam.nospam> wrote in message
> news:#d#A3weQFHA.3456@TK2MSFTNGP10.phx.gbl...

>> Ok, good luck. FYI - you do not need to have Office (or Access)
>> installed
>> on the machine with the database housed on it, that's what MDAC is for.
>>
>>
>> "Jason James" <jason.nospam@dive--master_nospam.org> wrote in message
>> news:OOTTDQeQFHA.2972@TK2MSFTNGP14.phx.gbl...

>> >
>> > Scott,
>> > I tried it again on a different machine running VS.Net and
>> > MS WIndows 2K and MS Office 2K (not 2003). Gave ASPNET
>> > read and write to the DB file only (not the folder), it is
>> > contained in a folder that is not a virtual directory, and
>> > everything worked just fine. I am going to try again on my
>> > other machine (running XP and MS Office 2003) and see what
>> > happens. If ther are no known issues with MS Office 2003
>> > and Windows XP then I must have done something stupid.
>> > I'll let you know in a while.
>> >
>> > Many thanks for sticking with me on this.
>> >
>> > Jason.
>> >
>> >
>> > *** Sent via Developersdex [url]http://www.developersdex.com[/url] ***

>>
>>

>
>

[Jason James]

Hi all,

thanks for all your help on this. I got there in the end. Funny how
it worked in a windows app and not a webservice though!

Regards,

Jason.

On Mon, 18 Apr 2005 17:11:27 -0400, "Scott M." <s-mar@nospam.nospam>
wrote:

>Yep. What "could not find installable ISAM" means is that the compiler
>couldn't find the provider specified in the connection string. There are
>only 2 reasons it would say that: either the provider is correct, but not
>installed on the machine or the connection string is incorrect.
>
>
>"Amil" <AmilHanish@hotmail.com> wrote in message
>news:%23WBn9KFRFHA.204@TK2MSFTNGP15.phx.gbl...

>>I just had this last night as well. Turned out to be the connection
>>string;
>> you MUST be very careful for exact format using using "JET OLEDB:..."
>> elements. In my case, it was a space after the : character :-(
>>
>> Amil
>>
>> "Scott M." <s-mar@nospam.nospam> wrote in message
>> news:#d#A3weQFHA.3456@TK2MSFTNGP10.phx.gbl...

>>> Ok, good luck. FYI - you do not need to have Office (or Access)
>>> installed
>>> on the machine with the database housed on it, that's what MDAC is for.
>>>
>>>
>>> "Jason James" <jason.nospam@dive--master_nospam.org> wrote in message
>>> news:OOTTDQeQFHA.2972@TK2MSFTNGP14.phx.gbl...
>>> >
>>> > Scott,
>>> > I tried it again on a different machine running VS.Net and
>>> > MS WIndows 2K and MS Office 2K (not 2003). Gave ASPNET
>>> > read and write to the DB file only (not the folder), it is
>>> > contained in a folder that is not a virtual directory, and
>>> > everything worked just fine. I am going to try again on my
>>> > other machine (running XP and MS Office 2003) and see what
>>> > happens. If ther are no known issues with MS Office 2003
>>> > and Windows XP then I must have done something stupid.
>>> > I'll let you know in a while.
>>> >
>>> > Many thanks for sticking with me on this.
>>> >
>>> > Jason.
>>> >
>>> >
>>> > *** Sent via Developersdex [url]http://www.developersdex.com[/url] ***
>>>
>>>

>>
>>

>
>