O$ - DAM issue - differences between dev and runtime

David Walton omuser at charlie.housing.admin.nyu.edu
Mon Apr 6 20:24:00 EDT 2009

Okay... no responses. Let's try again.

I have a table method that is called $update. It processes some  
history, checks that the user has changed some values, then says  "Do  
default" with a return value. The problem is that I get different  
results from the return value on the do default in runtime than in  

Can someone tell me what I should expect from the return value on a do  
default? Is it boolean, numeric, etc? It seems to be returning a blank  
(like '').


On Apr 4, 2009, at 6:44 AM, David Walton wrote:

> Hi,
> I'm testing a runtime of my library using the mysql dam. It works  
> fine when I'm in development but not in runtime. It also seems to be  
> specific to mysql. Here's the issue.
> I have a table class which issues a Do default (returning #F) during  
> a delete or an update. When in runtime, the flag returns false even  
> though the update or delete is successful. This doesn't happen in  
> development. Could anyone offer me a clue as to why this might occur?
> The code looks like this:
> Do default Returns #F
> If flag false
>  OK message  {Unable to update [itablename] [tref.$errortext()].}
>  Do tref.$rollback()
>  Quit method kFalse
> Else
>  Do tref.$commit()
> End If
> Thanks.
> _____________________________________________________________
> Manage your list subscriptions at http://lists.omnis-dev.com

More information about the omnisdev-en mailing list