Not sure if this will help, but I had a similar issue sometime last year. I was able to confirm that the DB was changing via setData(), but a subsequent read returned old data. Turns out that fourQ has some built-in caching. Note that this only occurred when I did a getData(), setData(), getData() all in a single request.
I made a tweak for fourQ's getData() (optional param) overriding the caching mechanism. HTH, Scott Blair McKenzie wrote: > I've had this problem with compound array properties, until I realised > you had to pass in extra property to deal with that data properly. > Can't remember if setData or getData was the problem. > > Blair > > On 5/22/07, *Hoolahawk* <[EMAIL PROTECTED] > <mailto:[EMAIL PROTECTED]>> wrote: > > > Hi, > > I am using setData to update a record in the DB, but we I get the data > after, it hasn't updated. Any suggestions? > > Kind Regards > > David > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "farcry-dev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/farcry-dev?hl=en -~----------~----~----~----~------~----~------~--~---
