Running Embedded Procedures in Access 2003

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

Guest

I have a problem that is only showing up in Office 2003 with running a
VisualBasic created "Embedded Procedure" from MS Access. It calls an https
update from another server (outside of our domain).

It works with Windows 2000 and Office XP, but does not work with Office
2003. Any thoughts at all?

Thanks!
 
Hi, David.
It works with Windows 2000 and Office XP, but does not work with Office
2003. Any thoughts at all?
Click to expand...

Yes. "I wonder what error message David is getting from Access 2003."
Others are probably wondering the same thing, because a number of people
more experienced than I have seen your message too, and none of them have
replied to your post.

HTH.

Gunny

See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips.

(Please remove ZERO_SPAM from my reply E-mail address, so that a message
will be forwarded to me.)
 
I'm also wondering what an 'Embedded Procedure' might be, and what an 'https
update' might mean. I know what HTTPS is, but what is being updated by what?
Is the Access app attempting to send data to a web app, retrieve data from a
web app ... ?

I'm also wondering whether the Access 2003 app is running on the same system
as the Access 2002 app? If not, it may not be an Access issue at all, it may
be a system/OS configuration/security issue.

--
Brendan Reynolds (MVP)
http://brenreyn.blogspot.com

The spammers and script-kiddies have succeeded in making it impossible for
me to use a real e-mail address in public newsgroups. E-mail replies to
this post will be deleted without being read. Any e-mail claiming to be
from brenreyn at indigo dot ie that is not digitally signed by me with a
GlobalSign digital certificate is a forgery and should be deleted without
being read. Follow-up questions should in general be posted to the
newsgroup, but if you have a good reason to send me e-mail, you'll find
a useable e-mail address at the URL above.
 
Gunny,

To provide a bit more information in the hopes of a clue....

The error message results from attempting to run a macro that calls the
"Embedded Procedure" in MS Access. The procedure, which is what MS Access
calls a module written in VisualBasic invokes a series of XML queries, vis
https, between our SQL/IIS server and another here on campus to update data.

The error message itself is almost no help at all. It claims to be generated
by MS Office and it reads simply "Unable to connect to server using
https://blah blah blah". No other help is offered, and nothing is left in the
error log on the client or server.

In comparison, I can take the https URL and paste it into IE or Firefox on
any Windows XP system and it WILL connect successfully to the remote server
and update the records. So far the problem is limited to Windows XP systesm
however. As a test I removed Office 2003 and installed Office XP and the
macro still would not run and generated the same error.

I do not believe that it is related to the Internet Security or Trusted
Zones security in Windows XP as the XML request WILL run in IE.

Any more help?

Thanks!

David
 
Hi, David.
a module written in VisualBasic invokes a series of XML queries, vis
https, between our SQL/IIS server and another here on campus to update
Click to expand...
data.

I'm not familiar with Access's use of XML queries as yet, so I may not be
much help to you. I'm not sure of anyone else who hangs around the Access
security newsgroup and may be familiar with XML queries and troubleshooting
them, either. Perhaps posting a question about "Connection problem with XML
queries" in the Microsoft.Public.Access.Queries newsgroup will turn up
someone knowledgeable in this area.
In comparison, I can take the https URL and paste it into IE or Firefox on
any Windows XP system and it WILL connect successfully to the remote server
and update the records.
Click to expand...

This connection is apples to oranges when compared to Access's ability to
connect to a data source. Being able to connect via the Web browser is good
news, because it means there's a network connection. It doesn't mean,
however, that Access can get through as well. Access needs to be able to
"talk" to the data source via Jet, the database engine, using the
appropriate connection, drivers and network protocols. The DSN (if that's
what your application is using) may not be configured correctly on this
computer, which would prevent a connection to the server.

Check for a DSN and, if there is one, compare it to the DSN used by the
other Windows 2K computers. If you don't know what a DSN is, then get a DBA
to help you determine what information needs to match with the DSN's on the
other computers for it to work on the Windows XP computer, too.
As a test I removed Office 2003 and installed Office XP and the
macro still would not run and generated the same error.
Click to expand...

As Brendan Reynolds mentioned earlier in this thread, it may be an OS
configuration/security issue, not an Access issue. Since you know that it
doesn't work for either Access version on this computer while it works on
other computers, you've found a strong indicator that either the DSN or the
OS settings on this computer don't match those of the other Windows 2K
computers. That's where I would start my investigation if the DSN is
determined to be fine (or not an issue) if I were in your shoes. The
Microsoft.Public.Access.Queries newsgroup may have some suggestions for you
on what to check.

I'm going to be offline for the next five or six hours, so perhaps someone
else may be able to help you on this thread in the meantime.

HTH.

Gunny

See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips.

(Please remove ZERO_SPAM from my reply E-mail address, so that a message
will be forwarded to me.)
 
Back
Top