By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
454,968 Members | 1,215 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 454,968 IT Pros & Developers. It's quick & easy.

Link to data on CD

P: n/a
I need to programmatically create a link to a table in an MDB on a CD, so I
can read data from it.
Access objects that it can't create an LDB file in the same directory as the
MDB.
Is there any way I can write the linked table's Connect property (I'm using
DAO) to force exclusive access for this MDB? (That way no LDB would be
necessary.)

Or is there another solution possible?
- Turtle
Nov 13 '05 #1
Share this Question
Share on Google+
7 Replies


P: n/a
On Fri, 28 May 2004 00:03:57 GMT, "MacDermott" <ma********@nospam.com>
wrote:

Not sure if this would work, but try the /readonly command line
argument for msaccess.exe

-Tom.

I need to programmatically create a link to a table in an MDB on a CD, so I
can read data from it.
Access objects that it can't create an LDB file in the same directory as the
MDB.
Is there any way I can write the linked table's Connect property (I'm using
DAO) to force exclusive access for this MDB? (That way no LDB would be
necessary.)

Or is there another solution possible?
- Turtle


Nov 13 '05 #2

P: n/a
On May 28 2004, 05:30 am, Chuck Grimsby
<c.*******@worldnet.att.net.invalid> wrote in
news:4c********************************@4ax.com:
On Fri, 28 May 2004 00:03:57 GMT, "MacDermott" <ma********@nospam.com>
wrote:
I need to programmatically create a link to a table in an MDB on a CD,
so I can read data from it.
Access objects that it can't create an LDB file in the same directory
as the MDB.
Is there any way I can write the linked table's Connect property (I'm
using DAO) to force exclusive access for this MDB? (That way no LDB
would be necessary.) Or is there another solution possible?


In Message-ID 3B***************@uibk.ac.at, Helmut Kalb discovered
that the secret is to use the undocumented /EMBEDDING switch.


But this only helps to prevent the "read-only" message when opening the
database from CD. The OP is trying to link to a database on CD, not open it
in the Access UI. When opening the linked table, Access attempts to create
the ldb file for the database on CD, which fails.

--
remove a 9 to reply by email
Nov 13 '05 #3

P: n/a
Great idea, Tom,
but how do I use that when I'm trying to create a link programmatically?

"Tom van Stiphout" <to*****@no.spam.cox.net> wrote in message
news:qm********************************@4ax.com...
On Fri, 28 May 2004 00:03:57 GMT, "MacDermott" <ma********@nospam.com>
wrote:

Not sure if this would work, but try the /readonly command line
argument for msaccess.exe

-Tom.

I need to programmatically create a link to a table in an MDB on a CD, so Ican read data from it.
Access objects that it can't create an LDB file in the same directory as theMDB.
Is there any way I can write the linked table's Connect property (I'm usingDAO) to force exclusive access for this MDB? (That way no LDB would be
necessary.)

Or is there another solution possible?
- Turtle

Nov 13 '05 #4

P: n/a
Thanks, Dimitri!

That's my problem exactly.

Ideas, anyone?

- Turtle

"Dimitri Furman" <df*****@cloud99.net> wrote in message
news:Xn****************************@127.0.0.1...
On May 28 2004, 05:30 am, Chuck Grimsby
<c.*******@worldnet.att.net.invalid> wrote in
news:4c********************************@4ax.com:
On Fri, 28 May 2004 00:03:57 GMT, "MacDermott" <ma********@nospam.com>
wrote:
I need to programmatically create a link to a table in an MDB on a CD,
so I can read data from it.
Access objects that it can't create an LDB file in the same directory
as the MDB.
Is there any way I can write the linked table's Connect property (I'm
using DAO) to force exclusive access for this MDB? (That way no LDB
would be necessary.) Or is there another solution possible?
In Message-ID 3B***************@uibk.ac.at, Helmut Kalb discovered
that the secret is to use the undocumented /EMBEDDING switch.


But this only helps to prevent the "read-only" message when opening the
database from CD. The OP is trying to link to a database on CD, not open

it in the Access UI. When opening the linked table, Access attempts to create
the ldb file for the database on CD, which fails.

--
remove a 9 to reply by email

Nov 13 '05 #5

P: n/a
Take a look at
http://support.microsoft.com/default...b;en-us;208431

If that doesn't work, here's something else you can try: Before creating a
link, use SetOption to programmatically change the default database open
mode from shared to exclusive. Most likely, it applies only to databases
opened in Access UI, but it's worth a try.

On May 28 2004, 09:39 pm, "MacDermott" <ma********@NoSpam.com> wrote in
news:lR*******************@newsread1.news.pas.eart hlink.net:
Thanks, Dimitri!

That's my problem exactly.

Ideas, anyone?

- Turtle

"Dimitri Furman" <df*****@cloud99.net> wrote in message
news:Xn****************************@127.0.0.1...
On May 28 2004, 05:30 am, Chuck Grimsby
<c.*******@worldnet.att.net.invalid> wrote in
news:4c********************************@4ax.com:
> On Fri, 28 May 2004 00:03:57 GMT, "MacDermott" <ma********@nospam.com>
> wrote:
>>I need to programmatically create a link to a table in an MDB on a CD,
>>so I can read data from it. Access objects that it can't create an LDB
>>file in the same directory as the MDB.
>>Is there any way I can write the linked table's Connect property (I'm
>>using DAO) to force exclusive access for this MDB? (That way no LDB
>>would be necessary.) Or is there another solution possible?
>
> In Message-ID 3B***************@uibk.ac.at, Helmut Kalb discovered
> that the secret is to use the undocumented /EMBEDDING switch.
>


But this only helps to prevent the "read-only" message when opening the
database from CD. The OP is trying to link to a database on CD, not open
it in the Access UI. When opening the linked table, Access attempts to
create the ldb file for the database on CD, which fails.


--
remove a 9 to reply by email
Nov 13 '05 #6

P: n/a
Can't you copy the DB from the CD onto the local drive?

--
Michael Hopwood
"MacDermott" <ma********@nospam.com> wrote in message
news:Nl*****************@newsread3.news.atl.earthl ink.net...
I need to programmatically create a link to a table in an MDB on a CD, so I can read data from it.
Access objects that it can't create an LDB file in the same directory as the MDB.
Is there any way I can write the linked table's Connect property (I'm using DAO) to force exclusive access for this MDB? (That way no LDB would be
necessary.)

Or is there another solution possible?
- Turtle

Nov 13 '05 #7

P: n/a
Many thanks to all who replied here.

To the last question -
yes, if it were just me, I could copy from a CD to a local file.
But I'm writing this application for some folks who are not especially
technically inclined, and they will be receiving the source data on a CD,
so I'm trying to make it as easy as possible for them.

My face is a bit red now, because I'm pretty sure I've tracked the problem
down.
This being personal information, I had secured it pretty tightly with a
workgroup file.
In my zeal, I had removed permission for anybody but the "Administrator"
group to open the file exclusively.
Hope nobody else has this problem, but if you do -
check your permissions!

- Turtle

"MacDermott" <ma********@nospam.com> wrote in message
news:Nl*****************@newsread3.news.atl.earthl ink.net...
I need to programmatically create a link to a table in an MDB on a CD, so I can read data from it.
Access objects that it can't create an LDB file in the same directory as the MDB.
Is there any way I can write the linked table's Connect property (I'm using DAO) to force exclusive access for this MDB? (That way no LDB would be
necessary.)

Or is there another solution possible?
- Turtle

Nov 13 '05 #8

This discussion thread is closed

Replies have been disabled for this discussion.