Search results

Phil, Are the agents not releasing after the request is returned, or do you simply not have enough agents to service the request volume? Post the code where you make the appserver connection. - Jason For future reference, include the Progress Version and what OS you are using in posts.

You might be able to fix it by upgrading your OS to a supported version, and upgrading your Progress to supported version.

OpenEdge 11.6 Documentation

Went to download latest version and keep getting unexpected end of archive. Winrar and 7 zip

Post a code snippet. My Answer :- I know huge bits of legacy/other developers code can be pretty daunting. Just take the time to break it into chunks. eTime the queries, check the index's, make sure records are being read and used efficiently. What people do :- Buy faster hardware to mask...

Was a nice little pub almost opposite EMEA that had some good bottled craft beers. Think i tried 4 or 5 before settling on something. Cant remember what it was for the life of me though!

This is going straight to my boss :)

I might have the wrong end of the stick but i am assuming he was using pdf include in a native progress, client side application. (With his mention of workstations etc) Having experience of using com-handles this way i never noticed any performance issues with creating documents and interfacing...

Funny fact for server 2012. Create a proenv shortcut. Set the start-in parameter in properties to any directory. Double click the shortcut, proenv will be in the directory but no admin privilidge to do anything. right click run as admin. Proenv now has admin privilidges, but starts in...

I dont see the point in PDFinclude in a windows enviroment. Just use com-handles and open excel/word. You can use saveto and save as a PDF anyway, and it gives you more scope for layout etc. Oh and have fun when you upgrade to windows 10. It destroyed our V9 application.

What? Are you running progress client-server, with your business logic running on an AppServer?

So to elaborate slightly. DEFINE BUFFER bEmployee FOR Employee. FOR EACH Employee EXCLUSIVE-LOCK. FIND bEmployee where bEmployee.UniqueValue = Employee.UniqueValue NO-ERROR. BUFFER-COPY bEmployee to Employee. END. Now i realize this is pointless, as the source and target for...

I heard something new today, and being mr skeptical i wanted to validate. Buffer-Copy source to target wont cause any IO writes if the source and target are the same. Please validate/debunk. - Jase

Instead of assigning shared variables in the calling procedure, build a dynamic temp-table of the parameters and pass that temp-table to the .p as a single input param. That way you dont need to statically define data types. Just make sure you create your table data in a logical way, IE Record...

Take a look at the above knowledge base. You can use it to solve the shared variable issue. Using a mix of the two KB articles will resolve your form issue too.

Okay :) Todays clue. Progress KB - Temp-table Basics: Example code using a dynamic temp-table It wont do exactly what you need by copy and pasting but its enough of a shove in the right direction for you to sort it out.

Your variable declarations dont have to be dynamic, or even variables for that matter. What could you use instead? (Today's clue) Think outside the box for a bit and if you're still stuck tomorrow ill give you another clue.

Dynamic Queries will be your friend. Progress KB - How to use dynamic query - Sample code Read that, then understand that the entire query is a string and can be replaced with variables. I can get you some real life example code tomorrow when im in the office.

Yeah i found it in the end. But much anger from my part at progress changing the default behavior. If i wanted crappy opaque grey selected highlights i'd have turned it on somehow.

We had all of our progress browsers go an annoying grey colour instead of blue when using multi-select during a major upgrade. Took me a while to turn that crap off. My advice : - Test test test.