|
Home > Archive > MS Access and Internet > November 2005 > access on web server
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
access on web server
|
|
|
| 1. Microsoft knowledge base claims Access files on web/ftp servers can be
opened remotely. However, when I attept to open an Access file remotely, I'm
told I cannot use an ftp address, that I must use http, even though ftp
addresses already exist in My Network Places, and I can open those
connections. And when I put in the http address, I'm told the server cannot
be found. Any ideas?
2. When the database file on the Web server is opened and a temporary .ldb
file is created, the .ldb file remains open for long periods of time, even
though no one is accessing the .mdb file. This prevents me from overwriting
the file with a newer version. Is there some way I can force the file to
close and get rid of the .ldb file, or set a time limit so it expires after a
certain amount of inactivity?
--
larry
| |
| Douglas J. Steele 2005-11-03, 8:30 pm |
| "larry" <larry@discussions.microsoft.com> wrote in message
news:D2A32096-4A8A-4561-85D0- 1CC460D4C247@microso
ft.com...
> 1. Microsoft knowledge base claims Access files on web/ftp servers can be
> opened remotely. However, when I attept to open an Access file remotely,
> I'm
> told I cannot use an ftp address, that I must use http, even though ftp
> addresses already exist in My Network Places, and I can open those
> connections. And when I put in the http address, I'm told the server
> cannot
> be found. Any ideas?
How are you trying to open them? It's not as simple as putting a URL instead
of a UNC. Carl Prothman has the necessary information at
http://www.carlprothman.net/Technol...3/Default.aspx,
but note his comments about the method being considered obsolete.
> 2. When the database file on the Web server is opened and a temporary .ldb
> file is created, the .ldb file remains open for long periods of time, even
> though no one is accessing the .mdb file. This prevents me from
> overwriting
> the file with a newer version. Is there some way I can force the file to
> close and get rid of the .ldb file, or set a time limit so it expires
> after a
> certain amount of inactivity?
Are you sure you're closing alll connections to the database? The file
should go away once all the connections have been closed.
--
Doug Steele, Microsoft Access MVP
http://I.Am/DougSteele
(no e-mails, please!)
|
|
|
|
|