Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Should I update to SP2
Message
 
 
To
23/10/2007 23:17:14
General information
Forum:
Visual FoxPro
Category:
Other
Environment versions
Visual FoxPro:
VFP 9 SP1
OS:
Windows XP SP2
Database:
Visual FoxPro
Miscellaneous
Thread ID:
01262331
Message ID:
01263040
Views:
25
>>Bernard,
>>
>>It bombs for me too with:
>>
>>---------------------------
>>XML Web Services Publisher Error
>>---------------------------
>>Field TIPS does not accept null values.
>>
>>
>>
>>Location: oweb
>>
>>Number: 1581
>>
>>Method: addfoxcode
>>
>>Message: INSERT INTO (THIS.cWSAlias) (Type, Name, Menu, Tips, URI, WSML, Class, Port, TimeStamp, UniqueID, Toolbox, Comfile, Prefs) VALUES("C", lcWSName, lcMethodStr, lcTipsStr, lcWSDL, lcWSMLGTM, lcClass, lcServicePort, ldDateTime, lcID, .T., lcServiceDoc, lcMethodStr2)
>>
>>Line: 224
>>
>>______________________________
>>
>>Press OK to ignore error and continue.
>>
>>Press Cancel to close.
>>
>>
>>---------------------------
>>OK Cancel
>>---------------------------
>>
>>This SP2 is quickly becoming the worst experience for me regarding software updates.
>>
>>Mike
>>
>>
>
>Hi Mike
>
>Dont ask me how but although the code in the SP1 and sp2 FFC classes for this class is identical, somewhere else something is amiss.
>
>Anyway after much debugging I have come up with a fix. This will fix this error and also allow the TaskPane to work properly.
>
>Fix
>
>1. Open the class HOME()+"ffc\_ws3utils.vcx" and select the _webservice class for editing
>
>2. Open the method "addfoxcode"
>
>3. Scroll down till you see this code:
>
>lcServiceDoc = ""
>THIS.cWSname = loService.Name
>lcWSName = THIS.cWSname
>lcServiceDoc = loService.Documentation  <<<--- this is the culprit
>
>
>The above marked line sometimes returns a null and this is stored in lcServiceDoc, later on causing an error.
>
>4. Change this offending line to:
>
>lcServiceDoc = NVL(loService.Documentation,"")
>
>
>5. Voila!. No more error and the Taskpane also works properly.
>
>One down many more to go....
>
>Bernard

Thanks a lot for sharing this info.
If it's not broken, fix it until it is.


My Blog
Previous
Reply
Map
View

Click here to load this message in the networking platform