On 1 Jul 2017, at 12:12 am, Stephen J. Orth via 4D_Tech <4d_tech@lists.4d.com>
wrote:
>
> I am getting an array range check error on the following line:
>
> If (Size of array(as_function)>=1)
>
> This is a compiled application, so how does this type of error even exist
> for this line?
>
Michael,
The best I've found is the JSON functionality in Rob Laveaux's NTK plug in:
http://www.pluggers.nl/product/ntk-plugin/
Miyako also has a plugin on github: https://github.com/miyako/4d-plugin-json
I've used them both. Miyako's is fully capable and if you can't justify the
cost of NTK you
It's our standard design to do test "In Transaction" and Trigger Level in
trigger. We never used cascade trigger either.
Error handling in trigger is also standard in our design. We have to create
large error code base for error interpretion in multiple language.
Alan Chan
4D iNug Technical
Yes, having UI in transaction is not ideal (at least in our design) and that's
why we never used that approach.
Update pricing is pretty routine for us as well (in our retail module) but we
never need nested transaction.
if no ui is involved,
Master transaction
nested transaction 1 for task
Hi Peter,
I never used component and have no idea what complication would it be in
transaction. Nonetheless, we do a lot of updates from time to time. We only use
normal transaction and trigger even for millions of records. We normally split
into 5,000 to
10,000 records per transaction. I
I’d like the source code, but compiled is OK with good documentation.
Thanks for any response,
Michael Ferguson
MyOfficelink
**
4D Internet Users Group (4D iNUG)
FAQ: http://lists.4d.com/faqnug.html
Archive:
Transactions around a UI can be very useful.
When it is necessary to drill down many levels, it gets to be very difficult,
or impossible to 'undo' an action when needed.
for example in my system we track animals (research).
for each animal, there are a lot of related data.
- Cages, where there
Alan,
I have a slightly different take from Peter's - consider attempting to make
changes in a database with many users who may or may not be 'touching' or
accessing data involved in the chain of updating. Inventory updates are a
classic example. Pricing can be another. Ideally these sorts of
On 2 Jul 2017, at 18:44, Alan Chan via 4D_Tech <4d_tech@lists.4d.com> wrote:
> If there's no UI, why you need nested transaction?
I’ve never considered transactions as a UI tool (mainly because it’s a bit of a
nightmare matching the scope of the opening and closing points) but I
acknowledge
If I understand nested transaction correctly, it's like creating an invoice
master in a transaction (remain opened), then add invoice line item in nested
transaction (start and end nested transaction in one go), add nth line of
invoice items in new
nested transaction continously. Failure of one
On 2 Jul 2017, at 00:12, Alan Chan via 4D_Tech <4d_tech@lists.4d.com> wrote:
> It's a great feature if long transaction that holding up records isn't an
> issue to your operation. Of course, make sure no one would take coffee in the
> middle of a transaction:-)
Hi Alan
They execute in
11 matches
Mail list logo
