how do you change IUSR_machinename permissions?

[Nathon Jones]

Having a nightmare with the old DW bug when using an Access database and ASP
pages that produces this error:

"Could not open "unknown"; file arleady in use."

Almost all of the tech support advice I have been offered so far has been
about changing permissions....but none explain HOW you change the
permissions, just that you should (very helpful).

Can someone run that past me?

I am convinced that permissions is NOT the problem here. The problem is
that every time you open a Recordset on an ASP page, DW creates an .ldb file
in the same directory as the database. Yet, when you close the recordset
AND the asp page, the .ldb remains, which causes the error when you try to
preview the site.

My question is...

Why doesn't Dreamweaver delete the .ldb file once the recordset and asp page
have been closed?

Really confusing....hope someone can help
Nath.

[Lionstone]

There's a simple workaround.
Make a page that connects to a different database. The database can be
empty, but you need to have a table in it. Call your page lockrelease.asp
or something. All it has to do is request a recordset. No display
necessary. Open that page with DW. Even though it doesn't release its
locks normally, if you open a page that connects to a different database, it
will release the locks on the first database.

--
-------------------------------------------------------------------
You must SHOW YOURSELF to e-mail me. No cowards allowed!




"Nathon Jones" <nathon@SHPAMkirkmoor.com> wrote in message
news:d32rrr$4k1$1@forums.macromedia.com...

> Having a nightmare with the old DW bug when using an Access database and

ASP

> pages that produces this error:
>
> "Could not open "unknown"; file arleady in use."
>
> Almost all of the tech support advice I have been offered so far has been
> about changing permissions....but none explain HOW you change the
> permissions, just that you should (very helpful).
>
> Can someone run that past me?
>
> I am convinced that permissions is NOT the problem here. The problem is
> that every time you open a Recordset on an ASP page, DW creates an .ldb

file

> in the same directory as the database. Yet, when you close the recordset
> AND the asp page, the .ldb remains, which causes the error when you try to
> preview the site.
>
> My question is...
>
> Why doesn't Dreamweaver delete the .ldb file once the recordset and asp

page

> have been closed?
>
> Really confusing....hope someone can help
> Nath.
>
>

[Tom Coleman]

right-click on the folder (directory) that the database lives in and go
to "properties", check "full control" for IUSR under the security tab.

You might have to restart you browser and/or DW to see any difference.

Not really a DW bug, though.

HTH,
Tom

Nathon Jones wrote:

> Having a nightmare with the old DW bug when using an Access database and ASP
> pages that produces this error:
>
> "Could not open "unknown"; file arleady in use."
>
> Almost all of the tech support advice I have been offered so far has been
> about changing permissions....but none explain HOW you change the
> permissions, just that you should (very helpful).
>
> Can someone run that past me?
>
> I am convinced that permissions is NOT the problem here. The problem is
> that every time you open a Recordset on an ASP page, DW creates an .ldb file
> in the same directory as the database. Yet, when you close the recordset
> AND the asp page, the .ldb remains, which causes the error when you try to
> preview the site.
>
> My question is...
>
> Why doesn't Dreamweaver delete the .ldb file once the recordset and asp page
> have been closed?
>
> Really confusing....hope someone can help
> Nath.
>
>

[darrel]

> Having a nightmare with the old DW bug when using an Access database and
ASP

> pages that produces this error:

I suggested this already, slightly with toungue in cheek, but I guess I'd
give it serious consideration...have you considered using MySQL instead?
Unless you have a specific nead for Access (like it's the only database your
web hosts allows), there isn't a strong reason to stick with it.

> Why doesn't Dreamweaver delete the .ldb file once the recordset and asp

page

> have been closed?

My guess is that DW needs to keep it open so you can do all of the WYSIWYG
database connection code writing.

One option is to use two connection strings and duplicate the database.
Store this string in a standalone file. On your local site, have it connect
to DB1. On your remote site, have it connect to DB2. Then, just be sure not
to overwrite the file that is storing the connection string on the server.

-Darrel