Search results

If you want to archive the records, then you want to move them, not delete them. But, think carefully since moving records to an archive table almost inevitably leads to a query across both tables which can be messy compared to a simple query on one table. BUT! This The problem is because...

You might start by rethinking the delete. What are you hoping to accomplish? Disk space is cheap. Data deleted is data lost.

And, I would start exploring OO programming in ABL. It really is the best way to encapsulate logic and shared data.

And why not send the error message to a common component, preferably an object, and have that component manage the stream ... or whatever you use. Note that with a common, shared error message component you can choose at any time to change the implementation and you only need to touch one place.

My remark from 9 years ago still stands...

So, have you asked the Gantt Chart source if there is a later version?

You beat me to it, James! I was just about to point out that biting the bullet and making the transition to OO would make most of these issues go away while providing a cleaner and more well-structured environment.

Your requirements are very unclear.

I.e., editing with too high a version might corrupt the file?

Does "we have installed" mean that it actually works reliably. In any case, it won't be supported.

Going forward, what is the best way to bring issues to your attention?

Some other things you might try https://x.com/chris4gl https://www.linkedin.com/in/christopherkelleher/ https://kelleher.social/@Chris The last one has a post 4 days ago.

Strange. I had an e-mail from Chris from the me.com address on 29 May.

I didn't expect him to be able to fix it, but thought he would know how to reach Chris.

Ask James

Does chris.kelleher@me.com not work?

mixed bag of 11.7.x to 12.x.x. Sounds like an excellent way to get in all sorts of difficult trouble.

I.e., it would help a lot if we knew the business problem you were trying to solve.

I recommend that you think carefully about what you really need. For example, I can understand wanting to undo everything about a customer and their orders, while leaving everything about all other customers and their orders, plus treating the delivery flow as a separate transaction. What you...

The solution, of course, is to change the transaction scope. Making the entire do block one transaction is obviously going to lock a LOT of records with those kind of numbers. What is not obvious is what scope is appropriate for your business needs. Possibly you could process the orders for...