Linked Table Manager is Blank

[Matt]

I just converted my database to 2007 from 03. The linked table manager is
blank, but when I open any form, the correct data is there. There are no
selections for tables in the linked table manager but if I choose select all
and prompt for a new location, I'm able to select a new location. When I'm
done however, I get this error message:

"Object variable or With block variable not set"

Please help, I'm at a complete loss.

 

[aaron.kempf]

Access isn't a real database.

You don't need to use the linked table manager-- you need to move to
SQL Server and just use ADP.

it is liberating to work with such a superior technology.

-Aaron

 

[Matt]

Thanks for the response. I have never used SQL Server. The draw I have to
Access is one, I can use it, and two I can distribute it to computers without
Access. This may be a possibility in SQL Server, but again, I don't know.
Short term however, I would like to fix the database I am working on, in
Access. I will look into SQL Server in the meanwhile.

 

[aaron.kempf]

SQL Server is easier to use than Access BS
And are you talking about the 'Access Runtime'?

Well SQL Server is free- the runtime is free-- You can use the Runtime
with SQL Server; you do know that right?

Sorry

-Aaron

 

[Gina Whipp]

Matt,

Since you converted your front-end to 2007 you will have to convert your
back end to 2007 in order for the linked table manager to see the tables.
(PLEASE, make a back-up first!) Access 2007 doesn't play well with previous
versions.

On another note, please ignore Aaron Kempf his answer to EVERYTHING is an
SQL Server!

 

[aaron.kempf]

I'm not so sure that I need your crap.

The answer to 'never having to deal with linked tables again' lies
directly in Access Data Projects and SQL Server.

Anything else is a waste of time.

Compact and repair?
WASTE OF TIME.

User Level Security?
WASTE OF TIME.

Access Replication?
WASTE OF TIME

Splitting into frontend and backend?
WASTE OF TIME.

Maintaining relationships in two different tiers?
WASTE OF TIME.

Maybe if you didn't waste so much time with this midget-sized database
crap-- then just maybe you'd be able to hold a decent conversation
about the benefits of SQL Server.

Until then-- you're not worthy to wash my feet.

-Aaron

 

[Gina Whipp]

Don't let the doorknob hit you on the way out!

--
Gina Whipp

"I feel I have been denied critical, need to know, information!" - Tremors
II

I'm not so sure that I need your crap.

The answer to 'never having to deal with linked tables again' lies
directly in Access Data Projects and SQL Server.

Anything else is a waste of time.

Compact and repair?
WASTE OF TIME.

User Level Security?
WASTE OF TIME.

Access Replication?
WASTE OF TIME

Splitting into frontend and backend?
WASTE OF TIME.

Maintaining relationships in two different tiers?
WASTE OF TIME.

Maybe if you didn't waste so much time with this midget-sized database
crap-- then just maybe you'd be able to hold a decent conversation
about the benefits of SQL Server.

Until then-- you're not worthy to wash my feet.

-Aaron

 

[aaron.kempf]

Please ignore everything that Gina says.

Her answer to EVERYTHING is jet / Access databases.

Jet / Access databases are not
reliable
performance
secure
accurate enough

for real world usage.

Sorry

-Aaron

 

[Matt]

I converted both ends. When I hover over the linked tables, it shows the
correct .accdb file. Yes I am using the Access runtime with my installer
package.

I am ignorant to SQL Server altogether. I have only ever really used (spent
an extended time using) any other programs than Access or Cache'. I don't do
this for a living, so I wouldn't claim to be as knowledgeable as anyone else

 

[BruceM]

Review the various postings of the person who "recommended" SQL Server. It
is just about his only piece of advice, regardless of the circumstances.
SQL Server has its place, but it also has its own groups. As you have
pointed out, you asked in an Access group for specific reasons.
I am not very familiar with Access 2007, but the error message you described
in your original post seems to be a VBA error message. What causes the
error to happen? Does your error handling identify the event that throws
the error?

 

[Matt]

Verbatim:
Click Linked Table Manager
(verified by hovering over links to check file name)
Open screen - it's blank
I can choose to select all, even though it's blank, so I did
I then check the prompt for new location box
Press Ok
Asks for new location, I select the one I want (I have even tried my backup
copy of the back end) press open
Return error from Linked Table Manager
<information>"Object variable or With block variable not set."<vbOkonly>
No other events happen, I just return to the blank Linked Table manager.

All forms and linked tables work fine, but I need to be able to redirect the
backend to a different location.

 

[aaron.kempf]

the most powerful form of MS Access is ADP.

This is an engine with SQL Server.

-Aaron

 

[aaron.kempf]

you need to link tables-- just like I need to gain 50 pounds.
It just doesn't need to happen.

You should upsize your db to SQL Server and use ADP. Then you wouldn't
be having this problem.
Sane people- -when their DB craps out-- move up the food chain to SQL
Server.

-Aaron

 

[rquintal]

Please ignore everything that Gina says.

Her answer to EVERYTHING is jet / Access databases.

Jet / Access databases are not
reliable
performance
secure
accurate enough

for real world usage.

Sorry

-Aaron

Only in the world in your dimensional warp.
Go away to your dimensional warp.
Don't go away angry, just go away.

 

[aaron.kempf]

you need to link tables-- just like I need to gain 50 pounds.
It just doesn't need to happen.

You should upsize your db to SQL Server and use ADP. Then you
wouldn't
be having this problem.
Sane people- -when their DB craps out-- move up the food chain to SQL
Server.


-Aaron

 

[aaron.kempf]

well you can either learn SQL Server (it is _EASIER_ than Access) or
your job can go to India.

grow some balls, kid

-Aaron

 

[BruceM]

As I said, I'm not very familiar with Access 2007. However, a Google groups
search has turned up a number of threads about a blank Linked Table Manager
("Linked Table Manager" blank or "Linked Table Manager" empty are some
search strings you could try), mostly in earlier versions, but perhaps the
suggested fixes will work with your situation. They involve modifying
registry settings in some cases, so of course back up the registry and
follow all suggested procedures if you go that route.
Here is a link to an article here with more information. This is the
general link, but there is something on the page about an empty Linked Table
Manager:
http://home.comcast.net/~cccsolutions/accesstips.html
This link shows how to use code to re-link the tables, bypassing the
Manager. I realize it doesn't address the problem, but it is a run-time
method that can be used whenever the database is opened:
http://www.mvps.org/access/tables/tbl0009.htm

 

[Matt]

For what it's worth, I can't see the linked tables in Access 2007 in an .mdb
file either. Also, if I click the analyzer I get the same error message.

 

[Matt]

Just in case anyone is still interested in this issue being resolved in
Access, I fixed it. Simple. Run>regsrv32.exe "c:\Program Files\Microsoft
Office 2007\Office 12\ACCWIZ.DLL" or which ever path your ACCWIZ.DLL
(MANDATORY choose the one that would be installed in the Office 12
subfolder). Shut down Access, reopen and viola! You can see the linked
tables. Now, this worked for me, and even the Northwind template was not
visible, so whatever causes that behavior was fixed this way. Please nobody
that does not understand what this is try it, I'm not going to be responsible
for crap!

 

[Gina Whipp]

Matt,

Sorry, I got tied up today but I see BruceM came to your aide plus some
detective work on your own! Great Work!