Search results

You're absolutely right. Turns out that our old programs assumed that they were connected to the appropriate DBs. I also found out that we could use CONNECT statements and database references in the same program only because they were dealing with two different databases - one connecting, the...

Hmm, I wondered if that was the issue, but we have old Progress code that can CONNECT to a database and reference it within the same file. Is this separation a new requirement?

Progress: 10.2b SP7 OpenEdge Architect: 3.4.2.R342_v20090122-9I96EiWElHi8lheoJKJIvhM3JfVsYbRrgVIWL OpenEdge OS: Windows XP Professional 2002 SP3 Server OS: SUSE Linux Enterprise Server 11 I’m trying to compile a few simple programs in OE Architect to verify that I can connect to the right...

Yes, you're right. It should read like this: db.st d [DIR]/db.d1 f 500000 d [DIR]/db.d2 f 500000 d [DIR]/db.d3 f 500000 d [DIR]/db.d4 f 500000 d [DIR]/db.d5 b [DIR]/db.b1

Thanks for your response, Tom! Sorry about the confusion; I meant to ask two somewhat unrelated questions, but the title thread suggests otherwise. Also, I was replacing the full paths of our database names, and I got sloppy. :) What size do you consider "very large?" Our largest...

Progress: 10.2b SP7 OS: SUSE Linux Enterprise Server 11 I'm updating an old shell script to back up our databases, and I'd like to increase our efficiency: The old script uses the following to transfer database files into another directory: /usr/dlc/bin/probkup online "$dir1" "$dir2" -red 5...