I'm not sure what documentation you are reading, the BASIC documentation says you CAN execute SQL statements from within a transaction. See page 96 of the Basic.pdf in you documentation under the heading Transaction Restrictions. It explicitly says you CAN EXECUTE a SELECT.
And I do know that my problem lies within Universe (or rather the RPC call to universe, that's why I posted it here... It's a bug in UO .NET.... I can do a transaction in a PICK account using BASIC programming and have SELECT statements in it without any problem, however doing the same from UO .NET blows the program up. I'm just looking for anyone how has played with UO .NET that might know of a workaround? -----Original Message----- It's nothing to do with .NET; it's a restriction within UniVerse itself. You can read about what is and isn't allowed while a transaction is active in the UniVerse BASIC manual; it's too long to reproduce here. ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/ ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/
