Search results

Sounds like you're trying to do it in the right way - using handles. You really need to post some code to show us what you are attempting to do at the moment, but one possible solution: 1. Parent window runs child window PERSISTENTLY, setting a handle. 2. Write an internal procedure in the...

With this kind of error, you should always search the online KB for the error number: http://progress.atgnow.com/esprogress/results.do Searching for error 8552 results in result ID 21607, which talks about various problems with appserver brokers being unable to register with the NameServer...

Also, you could wrap an appserver agent in a webservice layer (using the Progress WSA - Webservice Adapter). Then you could call the webservice from your web browser, ultimately resulting in an appserver agent executing a .p.

As the trigger fires, I want the process flow to stop while a window/dialog appears. Once the window/dialog closes, trigger execution should continue. This is going to take a wait-for or some other blocking statement, unless anyone knows of another technique? I can, for example, throw up a...

No problem. If you hit any more sticking points, just post. There's lots of ADM2 experience on this forum.

Hello all, I have an OCX widget - a VSFlexGrid. You can drag things around on this, so there's an OLEDragDrop trigger that fires whan an item is moved. When this trigger fires, I'd like to fire up a dialog-box (or window, or whatever) to capture some VITAL data about the user's change...

I don't think this question is about run-time links. The poster has just moved the SDO to a different directory, but objects generated based on the SDO will be using the orginal path. I've not seen a manual re-pathing of the SDO fail like this before. Perhaps the AppBuilder is "repairing"...

You have to do this manually. Open up the SDB in the procedure editor (or a bog-standard text editor) and search for the SDO filename. You should find references along these lines: DATA-FIELD-DEFS preprocessor Data Source in the _PROCEDURE-SETTINGS section Change the path to the SDO here...

Yeah, as Tom said this is pretty shonky code. It probably works in your environment because you compile in a similar environment to that which you intend to ship to. But better structure would result in truely portable code, removing the need to compile in different environments entirely. I...

Sure, This looks like an attempt to assign the name of the machine running the code to the variable lcComputer. The use of the WINDOW-SYSTEM preprocessor means that the first section of code will be compiled in if the machine doing the compiling is a character windowing system (unix, for...

No, I don't think that's right at all. Where in the docs have you seen this? The appserver agent is a seperate process entirely to your procedure window - two different clients, two different sessions. You connect to the appserver, returning a handle. Running a procedure ON the handle will...

I can't see the attachments, but I remember from your code you were doing hAppserver = session. This will screw you up. By doing this, you're connecting to the appserver, and then wiping the connection handle out with the current session handle, so you then try to run the .p locally from...

*shiver* These "legacy" (meaning rubbish) systems drive me crazy.

As Casper says, it would appear that you have configured a webspeed agent instead of an appserver agent. Similar, but not the same. When you created your new agent in Progress Explorer, which category did you use? "Webspeed" or "AppServer"?

How about shared variables? Got any of those? My current app is covered in them and they keep me awake at night.

I love the Profiler - amazingly useful. As Greg says, not great for monitoring over an extended period of time, but great if you see a specific problem and want to dig out the root cause without guessing with messages everywhere. By the way - I've never had a profiler file so large for just a...

Again, back to the appserver settings. Are you connecting the appserver agents to a database when they startup? You would usually specify a PF file in the Server Startup Parameters property in the Agent group in Progress Explorer. What have you put in here?

Hi there, I'll dive in here. What's the idea behind this line? This looks to be resetting hAppServer to be the handle of your current client session, which surely isn't what you want. I'd remove this unless you have a real reason for it. You haven't yet mentioned your appserver...

I agree with Tom. I've been working with ADM 1+2 for the last 7 years, and although it's great for rapid development, it's not flexible enough to cope with more recent demands for application flexibility. If I was going to sink some R&D time into something right now, I'd look at DLL and...

Deleted! Should read all posts first :-(