Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Still having problems with XMLToCursor()
Message
From
17/02/2004 14:07:47
 
 
To
All
General information
Forum:
Visual FoxPro
Category:
Other
Title:
Still having problems with XMLToCursor()
Miscellaneous
Thread ID:
00878043
Message ID:
00878043
Views:
51
Hi Y'all,

I have an app where a small XML string (embedded schema) is supposed to be transformed to a cursor via XMLToCursor() but it fails about half of the time for the users.

- the app sits on a Novell server
- the user's run WinXP Pro
- I did NOT put msxml3.dll, msxml3r.dll into the app's Novell directory

Users say that every 2nd time (or so) it works and every other time it does not. I searched MSFT and here and Wiki and it seemed like I needed to get an updated msxml3.dll onto the user's PC's. I found one and installed it (via a .wsi? file [Windows Installation script?] and it updated only two files:

msxml3.dll
msxml3r.dll

This did not solve the problem. Here are my questions:

1) Do I need to run "regsvr32 msxml3.dll" on each client PC? Do I need to uninstall msxml.dll and msxml2.dll as well?

2) My PC (Win2000Pro) has a msxml3a.dll as well. This does not get updated with the MSFT download - is it needed anymore? Should I manually place this on the user's PC's?

3) Would it be better to plunk the 2 (or 3) dll's into the Novell app's directory because maybe they would be found quicker by VFP instead of having to search along the PC's path to find them in \System32? Since this happens on and off, maybe it is just not finding the .dll's quick enough?

4) If I plunk them onto the Novell server, do I need to run RegSvr32 against msxml3.dll so that the client machine has a registered location in the registry? Do I also need to register msxml3r.dll?

Thanks....this has taken too long to figure out! Too bad MSFT did not have a tech bulletin on it (I cannot find one)!

Albert Gostick

P.S. Thanks to previous responders but still not there yet!
Next
Reply
Map
View

Click here to load this message in the networking platform