Access ADP Project - (disconnected)

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I have 10 people on a network who all use copies of the same .ADP project to
connect to SQL Server. I have full admin rights, both to the network
(domain) and SQL Server and have no problem with this .ADP file on any
computer but one Windows 2003 server. This server runs office and is used as
a sort of service that periodically emails and faxes reports out of the .adp
file.

I recently updated antivirus, sypware, Windows, Office and now when I open
the .ADP file I don't see any tables and it says (disconnected) in the title
bar. I've confirmed that the connection still works via the test connection
button. Also, I can still see the network. I have no problem on any other
computer when logging into the same domain with the same user account so it
can't be a user rights issue.

Any ideas? Thanks!
 
JD> I recently updated antivirus, sypware, Windows, Office and now when I
JD> open the .ADP file I don't see any tables and it says (disconnected) in
JD> the title bar.

perhaps a firewall?

Those security patches are in fact quite dangerous. You receive all sorts of
alerts when the next "security breach" is discovered; but you don't receive
a word when later they discover that their overnight fix broke windows. MS
issues an article on the support site, but you don't know it's there. The
probability to become a victim of the security breach is some fraction of
one percent; the probabiltiy to become a victim of the bug in the fix of the
breach is 100%.

Vadim Rapp
 
I have seen some other people having trouble with ADP 2003 on Windows 2003
Server and being unable to find a solution.

The only suggestion that I can make is to try with a full recompilation of
all modules by using the /decompile switch. Make sure also that there is no
missing or outdated reference. You can also create an empty ADP file and
imports everything into it, to make sure that nothing old or strange remains
there.

There is a newsgroup about ADP: m.p.access.adp.sqlserver .
 
Thanks for the replys. The problem is that the project runs fine on another
machine so it doesn't seem to be a compilation issue. Just incase, I tried
recompiling and it didn't fix it. I looked for the /decompilation switch and
couldn't find it. Was that something added in Office 2003? This is still a
2002 project. Maybe if I upgrade the problem will go away... but that'll
cost a lot.

The other angle, in an earlier reply, was that the windows update caused a
problem. I share your frusteration with the havoc that the windows updates
cause but I dont think this is the case here. I have another, identical,
computer that is also completely up to date and it isn't having the same
problem.

Does anybody know enough about the (disconnected) status to be able to
explain why I could successfully test my connection but still remain in
disconnected status?

Thanks, all, for your help!
 
Thanks for the replies.

The problem only happens on one computer so I'm afraid that the
recompilation won't work. Since I'm desperate, though, I gave it a try. It
didn't work but I couldn't find the /decompilation switch. Is that a 2003
thing? I'm still in 2002.

I can relate to the frusteration implicit in the previous post regarding
Windows Update but I don't think that is the culpret either. I have this
project running on an identical computer which is also fully up-to-date. And
the Connection Test button works.

Can anybody explain how the Test Connection button would work but the
project would not connect? I'm using the windows authentication method (same
user on both computers) so it isn't anything that is user specific.

Thanks, all, for your help!
 
Thanks for the replies.

The problem only happens on one computer so I'm afraid that the
recompilation won't work. Since I'm desperate, though, I gave it a try. It
didn't work but I couldn't find the /decompilation switch. Is that a 2003
thing? I'm still in 2002.

I can relate to the frusteration implicit in the previous post regarding
Windows Update but I don't think that is the culpret either. I have this
project running on an identical computer which is also fully up-to-date. And
the Connection Test button works.

Can anybody explain how the Test Connection button would work but the
project would not connect? I'm using the windows authentication method (same
user on both computers) so it isn't anything that is user specific.

Thanks, all, for your help!
 
For the /decompile switch, it's a startup parameter. You must create a
shortcut to MSACCESS.EXE and add this switch in the property of the
shortcut.
 
An easier way than the /decompile parameter to force a recompilation of all
modules is simply to add a dummy reference in the References dialog window
of the VBA window. Close this references dialog window to make sure that
Access notice the change, re-open it again and remove the previously added
dummy reference. Access will notice the change in references and recompile
all modules. After this step, you can also use the option Recompile under
the Debug menu to make sure that everything is fine.
 
Hello,
You wrote on Tue, 3 May 2005 10:02:06 -0700:

JD> Thanks for the replies.

JD> The problem only happens on one computer so I'm afraid that the
JD> recompilation won't work. Since I'm desperate, though, I gave it a
JD> try. It didn't work but I couldn't find the /decompilation switch. Is
JD> that a 2003 thing? I'm still in 2002.

run network monitor, it wil show ip traffic and what does not get through.
Must be something related to security - firewall, or ipsec.

Vadim Rapp
 
also, check what protocol is used to connect to sql server - use odbc applet
for that.
 
Back
Top