Recent content by JLovegren

  1. J

    Dump Reload Level I to II

    Thank you for the good information. I thought that since the After Imaging is handled in OE Explorer that re-starting the database from that console would enable the AI and AI archiver, etc. the same way it remembers the database location, server settings, etc. I need to update my procedure...
  2. J

    Dump Reload Level I to II

    From a data restore standpoint: If I need to restore from backup - I can simply do a prorest command and everything goes back to where it belongs due to the storage areas being defined within each table and that itself will be backed up and restored? In other words, if I am migrating to another...
  3. J

    Dump Reload Level I to II

    That's an excellent idea. I have already loaded the data to make sure all is currently where it should be. Testing now. I think I will do that although going through the prostrct create, copying the empty8, loading the definitions and then loading the data is not something that I will be...
  4. J

    Dump Reload Level I to II

    This is what I needed, gentlemen! Just a couple more questions: 1. I will modify the data definition file to work properly. Would it be quicker to load the revised data definitions into the target system and then re-load the data into the pre-existing structure? If so, do I need...
  5. J

    Dump Reload Level I to II

    I hate to ask an unsmart question but... Windows I did a dump of data and sequences of a v9.1 workgroup database with Level I storage and a load into a v12.8 workgroup database with Level II storage. I noticed that it appears that all of the data went into my schema area. I may not know how to...
  6. J

    After Image Autostart?

    Understood. My mark backed up is in the test environment.
  7. J

    After Image Autostart?

    Maybe not the smartest question - I should already know the answer but, here goes. Version 12.8; Workgroup Database; Windows Server 2025 Std. I have AI settings configured in the OE Explorer. Also, my database is set to start in multi-user mode by default. When the server restarts, I check and...
  8. J

    After Imaging Guide

    I am looking for a guide on how to manage AI. I am using 12.8 with Workgroup database, Windows. I have the AI Archiver setup and running - help by Progress DBA. But, now I am looking for some understanding. Like: Do I need to do certain things to properly reboot the server or can I just...
  9. J

    Progress Engineer vs. Independent Contractor

    I am "managing" an in-house developed ERP system, used by 50 people. It started in version 8 and went live in version 9.1e back in the early 2000's. I have had good support from my programmer but he has retired, left California and so I have been keeping it running with chewing gum and scotch...
  10. J

    Scroll Bars in a window's frame (from v9.1e)

    I am not smart enough to understand all of this. I will, however, see if i can understand by using. As soon as I size all of my windows. At this point, it seems that Progress changed how to render Windows elements in the gui so it is a long job ahead unless there is something else, like a...
  11. J

    Scroll Bars in a window's frame (from v9.1e)

    It is interesting. I deleted the image from the frame, then added it back and it scales properly now. I resized the image several times before this to no avail. Thank you for your help in this. Obviously, I have much to learn.
  12. J

    Scroll Bars in a window's frame (from v9.1e)

    the code did not do the trick. i am working the attachment next. Thank you!
  13. J

    Scroll Bars in a window's frame (from v9.1e)

    I couldn't find a solution, I believe this should be an old topic... Windows 2025 64-bit OpenEdge v12.8.7 I am updating the application code from v9 to v12. v9 login window vs v12 login window is shown below. I did some resizing but regardless of size, the internal frame doesn't fit into the...
  14. J

    Setup Level II Storage Guide

    That's a good assumption. wrkfiles are created to temporarily hold data for running reports. The system was designed for v9, at which time Actuate could be bundled with Progress. Actuate was SQL and, at the time, was too slow so we used preprocessors in 4GL to create the data and then Actuate...
Back
Top