B
BlockNinja
I've written up a nice little access form that does a few different things
like opening up an external database and telling you the links (since on
Access 2000 you can't expand the link manager window to see long link
filenames), and also do a nice little "query tracer" to trace back all of the
queries in a db to their original tables in a nice little treeview.
However, at work there's some mdb's on a directory that is read-only to me
(it's for our "production" databases since we're not on SQL Server yet), and
whenever I open them via db.OpenDatabase(myfilename,false,true) (exclusive
false, read-only true) it comes back saying "The recordset could not be
locked"... Yes I know I can't lock it, but I still want to open the db for
analyzing what's there. Any ideas? Right now I have to copy the db's to my
local drive, and we're talking about 600-800MB a piece here, and copying to
the local drive is largely frowned upon since it's a waste of space,
disorganized, etc etc etc (insert office politics battles).
like opening up an external database and telling you the links (since on
Access 2000 you can't expand the link manager window to see long link
filenames), and also do a nice little "query tracer" to trace back all of the
queries in a db to their original tables in a nice little treeview.
However, at work there's some mdb's on a directory that is read-only to me
(it's for our "production" databases since we're not on SQL Server yet), and
whenever I open them via db.OpenDatabase(myfilename,false,true) (exclusive
false, read-only true) it comes back saying "The recordset could not be
locked"... Yes I know I can't lock it, but I still want to open the db for
analyzing what's there. Any ideas? Right now I have to copy the db's to my
local drive, and we're talking about 600-800MB a piece here, and copying to
the local drive is largely frowned upon since it's a waste of space,
disorganized, etc etc etc (insert office politics battles).