[thelist] ASP: residual database files Follow Up

Chris W. Parker cparker at swatgear.com
Fri Jul 19 15:26:01 CDT 2002


i think it's the folder permissions issue. i checked and every but "full
control" and "modify(?)" were checked.

as of right now the database has nothing special in it, so i'm just
going to leave it alone.

but in the future, what user accounts should be included on the folder
when it comes to full control access? is there any account that should
specifically /not/ be there?


thanks,
chris.

> -----Original Message-----
> From: Mike Carlson [mailto:domitianx at domitianx.com]
> Sent: Friday, July 19, 2002 11:58 AM
> To: thelist at lists.evolt.org; thelist at lists.evolt.org
> Subject: RE: [thelist] ASP: residual database files Follow Up
>
>
> They are hanging around because of either or both of the
> following reasons:
>
> 1. The connection is still open by the webserver. Make sure you are
> destroying the connection object (MyConn.Close) and setting
> it to nothing
> (MyConn = Nothing). This should make the ldb files go away unless.....
>
> 2. Delete permisions are not granted on that directory. You
> need to have
> read, write and create permissions set on the directory that
> the database is
> in. Now, on web servers this is not a very secure scenario so
> you should put
> the databases in a folder outside of the website tree and
> then use the full
> system path when creating the connection and opening it.
>
> I usually create a folder outside of the root of the web site
> and grant the
> neccessary permission to that directory:
>
> c:\webstuff
>     \sitename
>          \databases - place access databases here (read/write/delete)
>          \htdocs - this is the root of the website
>
> This ensures someone cannot download the database if they now
> the URL to it
> and you are not granting write and delete permissions to a publically
> accessible folder.
>
> Mike
> http://www.uselessthoughts.com
>
>
> 	-----Original Message-----
> 	From: Chris W. Parker [mailto:cparker at swatgear.com]
> 	Sent: Fri 7/19/2002 1:43 PM
> 	To: thelist at lists.evolt.org
> 	Cc:
> 	Subject: RE: [thelist] ASP: residual database files Follow Up
>
>
>
> 	so then mike, would say that it is because i am not
> closing all my db
> 	connections or more likely that the directory does not
> have delete
> 	permissions?
>
> 	in the article you gave, microsoft suggests giving the
> db directory
> full
> 	control rights to the users that use the database. but
> at the same
> time
> 	set read only (or i guess, read and write) only
> permissions on the db
> 	itself. is this as simple as righ-clicking on the
> folder and setting
> the
> 	permissions and then righ-clicking on the db and setting the
> 	permissions?
>
>
> 	thanks for the info.
> 	chris.
>
> 	> -----Original Message-----
> 	> From: Mike Carlson [mailto:domitianx at domitianx.com]
> 	> Sent: Friday, July 19, 2002 11:34 AM
> 	> To: thelist at lists.evolt.org; thelist at lists.evolt.org
> 	> Subject: RE: [thelist] ASP: residual database files Follow Up
> 	>
> 	>
> 	> .lbd files are not log files. They are "lock" files. It tells
> 	> the database
> 	> who has what records open at what time. This is so a person
> 	> cannot update the
> 	> same record at the exact same moment in time. You cannot turn
> 	> it off if you
> 	> are sharing the database to more than one user, which you are
> 	> on the web. Its
> 	> one of the downsides of using Access. MS SQL does not use a
> 	> lock file. Its
> 	> all handled internally by the engine.
> 	>
> 	> Here is the lowdown on .ldb files:
> 	>
> 	>
> http://support.microsoft.com/default.aspx?scid=kb;EN-US;q136128
> 	>
> 	> Mike
> 	> http://www.uselessthoughts.com
> 	>
> 	>
> 	>       -----Original Message-----
> 	>       From: Jay Blanchard
> [mailto:jay.blanchard at niicommunications.com]
> 	>       Sent: Fri 7/19/2002 1:30 PM
> 	>       To: thelist at lists.evolt.org
> 	>       Cc:
> 	>       Subject: RE: [thelist] ASP: residual database
> files Follow Up
> 	>
> 	>
> 	>
> 	>       --
> 	>       [snip]
> 	>       They are database log files created by the M$ system
> 	> you are using.
> 	>       [/snip]
> 	>
> 	>       There are settings on Access and M$ SQL Server
> to disable the
> 	> creation of
> 	>       log files, if you want to disable them. Make sure you
> 	> keep back-ups!
> 	>
> 	>       Jay
> 	>
> 	>       "Rumors of my demise are greatly exaggerated"
> 	>
> 	>       *************************************
> 	>       * Want to meet other PHP developers *
> 	>       * in your area? Check out:          *
> 	>       * http://php.meetup.com/            *
> 	>       * No developer is an island ...     *
> 	>       *************************************
> 	>       --
> 	>       [ winmail.dat was deleted, please don't send
> 	> attachments with your
> 	> message. ]
> 	>       --
> 	>
> 	>
> 	>       --
> 	>       For unsubscribe and other options, including
> 	>       the Tip Harvester and archive of thelist go to:
> 	>       http://lists.evolt.org Workers of the Web, evolt !
> 	>
> 	>
> 	> --
> 	> For unsubscribe and other options, including
> 	> the Tip Harvester and archive of thelist go to:
> 	> http://lists.evolt.org Workers of the Web, evolt !
> 	>
> 	--
> 	For unsubscribe and other options, including
> 	the Tip Harvester and archive of thelist go to:
> 	http://lists.evolt.org Workers of the Web, evolt !
>
>
> --
> For unsubscribe and other options, including
> the Tip Harvester and archive of thelist go to:
> http://lists.evolt.org Workers of the Web, evolt !
>



More information about the thelist mailing list