No I am not. Does this ignore the error message and process the update
somehow?
Zac Spitzer wrote:
Are you checking the result as bellow
result=featureService.UpdateFeatures(resourceID, fCommand, false);
if (result.GetItem(0).GetPropertyType() eq 9)
result.GetItem(0).GetValue() // Silent FDO error messages!!!!
z
On Fri, Aug 1, 2008 at 2:14 AM, Zac Spitzer <[EMAIL PROTECTED]> wrote:
can you post some code to demonstrate the problem?
On Fri, Aug 1, 2008 at 2:05 AM, George McLean <[EMAIL PROTECTED]> wrote:
Hello,
I am a bit stuck in upgrading to 2.0.1 mainly due to the issues with adding
data to feature sources discussed in this thread:
http://www.nabble.com/Please-try-your-operation-later-as-the-resource-was-busy-to16392736.html#a18556960
My immediate issue is that I have a client that would really like to us FF
3.0 with my application. I see that either I need to find a way to apply the
fixes made in 2.0 for FF to 1.2 or find a way around the issues with
updating feature data.
I could look at the code for MG 1.2 and apply the changes made to 2.0 with
some guidance on where to start but I think I would rather find a fix for MG
2.0.
Any suggestions would be appreciated.
Thanks
George McLean
_______________________________________________
mapguide-users mailing list
[email protected]
http://lists.osgeo.org/mailman/listinfo/mapguide-users
--
Zac Spitzer -
http://zacster.blogspot.com (My Blog)
+61 405 847 168
_______________________________________________
mapguide-users mailing list
[email protected]
http://lists.osgeo.org/mailman/listinfo/mapguide-users
