Access 2003 runtime and MS Soap

[Sharat Koya]

I have produced an access adp project that we would like to distibute using
the package wizard. Everything works ok on a machine with access 2003
installed.

however when we install to a Windows XP SP1 machine we have found that we
have to install MDAC 2.8, MSXML and the office 2003 soap component that only
seems to exist on the Office 2003 CD. The adp file does make use of web
services using the office 2003 soap toolkit. Is there a SOAP runtime we can
deploy with the package? The error that pops up in access runtime is missing
mssoap3.dll

thanks for any time on this


Sharat Koya
Addenbrookes Hospital
Cambridge University NHS Foundation Trust
UK

 

[Brendan Reynolds]

Try the Microsoft Office 2003 Web Services Toolkit, which can be downloaded
at ...

http://www.microsoft.com/downloads/...8a-e1cf-48a3-9b35-169d819ecf18&displaylang=en

That's a long URL, and may get wrapped across more than one line by your
newsreader. If you have problems with it, try ...
http://tinyurl.com/5uoux

--
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.

 

[Sharat Koya]

But that would require other office compnents such as VBA and Access which
defeats the purpose of using access runtime?

Have MS done this on purpose so that Access Runtime cannot access web
services?

thanks.

 

[Brendan Reynolds]

The Access Runtime *is* Access. It is a version of Access with a few design
features disabled. I am not aware of any reason why the toolkit would not
work with the runtime. Have you tested it?

--
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.

 

[Sharat Koya]

Ah I see, ok I have a virtual pc setup and have the following

Windows XP SP1
Installed MSXML4
Installed MDAC2.8
Installed Access Runtime and the project from packed wizard output
Installed the MS Office 2003 Web Services Toolkit

but when I open the project I still get the error:

Your database or project contains a missing or broken reference to the file
'MSSOAP30.DLL' version 3.0?

I would have thought it was installed with the Web Services Tool kit?


Thanks for your quick responses on this, much appreciated.

 

[Arvin Meyer]

Missing and broken references are another issue. You'll either need to set
the reference in the adp to point to the installed location of mssoap30.dll
or install and register the dll in the same folder as you put your app (so
that it can find it).
--
Arvin Meyer, MCP, MVP
Microsoft Access
Free Access downloads:
http://www.datastrat.com
http://www.mvps.org/access

 

[Arvin Meyer]

One other possibility. If you are not using mssoap30.dll in your app,
uncheck the reference to it before building the install package.
--
Arvin Meyer, MCP, MVP
Microsoft Access
Free Access downloads:
http://www.datastrat.com
http://www.mvps.org/access

 

[Brendan Reynolds]

The reference does seem to be required when using the toolkit.

Sharat, you mentioned earlier that you had installed an 'Office soap
component' from the Office CD. My guess is that the installation routine on
the CD installs to a different location than the downloaded toolkit. I'm
currently searching my own system to determine how many copies of the DLL
are present. The search is still running, but I've already found two, one in
the Program Files\Common Files\Microsoft Shared\Office11 folder, and one in
the Program Files\Common Files\MSSoap\Binaries folder. My guess is that your
app has a reference to the copy in the Office11 folder, but your test
environment only has the copy in the MSSoap\Binaries folder.

--
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.

 

[Sharat Koya]

I tried placing the MSSOAP30.dll in with the project as it does use it. I
then tried to register it using "regsvr32 mssoap30.dll" and it failed.
But I ran the project anyway and access didn't give me the error this time
but when a web service is used by the project access crashes with the error
"Runtime Error"

 

[Sharat Koya]

I have just tried re-mapping the reference to the Program Files\Common
Files\MSSoap\Binaries instance of MSSOAP30.DLL but the project throws other
errors (on the dev machine with Office 2003) when trying the web service
that was origianlly setup by the web services toolkit for microsoft office.
It seems that the the two versions behave differently.

Would this mean that there is an MS Office Soap (the one I need to opeate
with runtime) and a more generalised verison of soap from MS?

The virtual PC only has the MSSoap\Binaries version of MSSOAP30.DLL and it
pops up with the cannot find reference error. It is strange especially as I
have installed the MS Office 2003 Web Services Toolkit. There is no DLL in
the folder "Program Files\Common Files\Microsoft Shared\Office11"

thanks
Sharat

 

[Brendan Reynolds]

I just tested the only Access app I have that uses a Web Service, and it
works with either the Microsoft Office Soap Type Library V3.0 (the one in
the Office11 folder) or the Microsoft Soap Type Library V3.0 (the one in the
MSSoap\Binaries folder). I tested it with the /runtime switch too. I'm not
sure what else to suggest at this stage, except that you mentioned, in an
earlier post, an attempt to register the DLL that failed. Possibly that may
have caused some registry problems. Possibly it might be worth starting
afresh with a clean testing environment? Sorry I can't be more definite,
it's always difficult to help with a problem that one can't reproduce.

--
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.

 

[Sharat Koya]

Ok thanks, I will closely inspect the code and check with another instance
of a virtual PC

thanks for your time

Sharat.

 

[Sharat Koya]

sorry, just to check. did you install access runtime on to a PC that doesn't
already have msaccess? or did you try the access database on a machine with
access 2003 already installed? My project works in this senario but not
where access runtime only is installed.

thanks

Sharat

 

[Brendan Reynolds]

I tested with the /runtime command line switch. I'm not in a position to
test a real runtime installation. However, I really think it is *very*
unlikely that using the runtime is the problem.

--
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.

 

[Sharat Koya]

I have just created a second test.adp project. This time it does nothing but
access a single web service and does nothing else. The web service setup was
done by the web service tool kit for office 2003.

It again worked fine on a PC with Full MSACcess 2003 installed with or
without the /runtime option.

I then went to my test PC again with only access 2003 runtime and it failed.
It came up with the same MSSOAP30.DLL error. I then tested this on another
machine with out full Access 2003 and same again.

Is there anyway of including the Office 2003 Soap version in the package
wizard or through a seperate install without installing Access 2003?

thanks

Sharat

 

[Brendan Reynolds]

I don't know. I notice that the download page says that support for the
toolkit is provided through the microsoft.public.office.developer.vba
newsgroup. If no one else answers here, you could try asking there.

--
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.

 

[Albert D. Kallal]

I then went to my test PC again with only access 2003 runtime and it
failed. It came up with the same MSSOAP30.DLL error. I then tested this on
another machine with out full Access 2003 and same again.

Likely, the references on your development pc are different. You might have
to install ms-access into a virtual pc, install the soap, and then set the
references to the soap....and then create the mde. If the location and setup
of the soap reference on your development pc is different then the target
PC, then you will have problems.

So, if the path names for the dll are not the same VERSION, or not in the
same location, then you will have a break in your references code. This
advice applies if you use a reference to Excel, Word, Outlook, or something
like the soap ad in.

As a result of this difficult problem, you should consider using late
binding here. I have not tried this with the soap ad in, but it should work.

 

[Sharat Koya]

Hi thanks for your response. I have tried copying both versions of the
DLL to the virtual PC but the MS Office one for some reason would not
register and when I tried the other MSSOAP.DLL (the one in prog
files\common\ms shared\mssoap\binaries) it threw runtime errors and
didn't seem compatible.

The only way the application will work is for MS Access 2003 and the
Office version of MSSOAP to be installed. But that would defeat the
purpose of Access runtime and would mean a bigger support headache for
us on the client rollout side.

Please could you tell me what you mean by a late binding?

Many thanks

Sharat Koya

 

[Brendan Reynolds]

Possibly there may be other, supporting DLLs or additional registry entries
required. Why not try running the 'setup.exe' file from the download page
rather than just copying the DLL?

Here's the URL for the download page, if you need it.

http://www.microsoft.com/downloads/...8A-E1CF-48A3-9B35-169D819ECF18&displaylang=en

--
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.

 

[Sharat Koya]

Unfortunately when ever I try that it does not come with MSSOAP30.DLL that
should be installed to "\Program Files\Common Files\Microsoft
Shared\OFFICE11"

The only thing that does install that DLL is the MS Office 2003 CD with the
SOAP component. It seems to be a catch 22 situation as I do not want to
install Office or access 2003 on the target machine - Just Runtime.