Re: Temp database wouldn't open from jump drive
- From: lesperancer@xxxxxxxxxx
- Date: 26 Jan 2006 03:51:42 -0800
folder permissions ?
read-only files on jump drive ?
if you rename the jump drive db from xxx.tmp to xxx.mdb, can you open
it with access ?
robert d via AccessMonster.com wrote:
> When my app starts up, it creates a temporary database. This temp database
> is created from a 'model' database that is in the same folder as the
> application. Because there is a model, the creation is essentially to just
> copy the 'model' database and give it the name of the application with the
> extension ".tmp".
>
> Then code opens the temp database and links to the tables. This has always
> worked flawlessly until today. Today, I needed to open my app on a client
> computer. So I copied all the necessary files to a folder on a "jump" drive.
> I then ran everything from the jump drive on the client's computer.
> Everything worked fine, but the links to the tables in the temp DB were not
> valid. The links could be seen in the database window, but clicking on them
> gave an error. When I went to the code that did this creation, it could be
> seen that the temp DB was created (this was verified by going to Windows
> Explorer to check the existence of the temp DB that was just created).
> Here's the relevant code:
>
> Set dbsTemp = wrkDefault.OpenDatabase(strTempDatabase)
> dbsTemp.TableDefs.Refresh
>
> If dbsTemp.TableDefs.Count < 1 Then
> dbsTemp.Close
> Set dbsTemp = Nothing
> Exit Sub
> End If
>
> At the line "If dbsTemp.TableDefs.Count < 1, the error "Object not set" was
> encountered.
>
> I found this very puzzling as all needed files were on the jump drive and in
> the correct folder, and most importantly, I could see that the tempDB
> (strTempDatabase) had been created.
>
> Now, without changing code, I took the same jump drive and plugged it into my
> laptop and opened the app from the jump drive. Everything worked just fine
> including linking to the tables in the temporary database.
>
> So, I'm stumped and I'm looking for some possible ideas as to what happened.
>
> Additional information: My laptop has Windows XP Home and the client machine
> is Windows 2000 Professional. The client machines have been "locked" down to
> some degree (i.e. executables cannot be run and downloading from the internet
> is very difficult). Is it possible that when I tried to connect to the temp
> DB on the jump drive that this was viewed as not allowed? I find that hard
> to understand, because my app was located on the jump drive and it was opened
> within Access which was on the client's machines.
>
> Finally, although I didn't have time to check this out: I've never had
> problems running my app (including creating the temp DB and linking to the
> tables in it) on my client's machine in the past. However, in the past all
> files have always been on the client machine's hard drive.
>
> Any ideas, thoughts, suggestions, appreciated.
>
> --
> Message posted via AccessMonster.com
> http://www.accessmonster.com/Uwe/Forums.aspx/databases-ms-access/200601/1
.
- Follow-Ups:
- Re: Temp database wouldn't open from jump drive
- From: robert d via AccessMonster.com
- Re: Temp database wouldn't open from jump drive
- References:
- Temp database wouldn't open from jump drive
- From: robert d via AccessMonster.com
- Temp database wouldn't open from jump drive
- Prev by Date: Re: strings
- Next by Date: Re: strings
- Previous by thread: Temp database wouldn't open from jump drive
- Next by thread: Re: Temp database wouldn't open from jump drive
- Index(es):
Relevant Pages
|