Search results

I can't speak 100%, but in my experience, they aren't even backwards compatible within the same service pack/revision. When we upgraded our test platform from 10.0b to 10.1b, I had to install both clients on any system that needed access (including ODBC access) to both live and test--the 10.1b...

That gives me a good start. It sounds like I don't need to move the archived extent back into the "current" ai extents--just reference the archived file. Any idea on A) If I can restore from my online weekday backups (that don't mark AI at all), and B) if so, how I tell what AI files I need to...

Thankfully, I've never had to do anything with our AI files. The one time I had a DB go really, really south, it was overnight and only a couple of hours after the nightly backup. Since the job scheduler restored to it's previous state anyway, I just let it get the overnight stuff caught up...

Not to beat a dead horse, but that's your problem--and it may justify moving to another ERP solution. I've never worked with a solution that used Progress that included direct support to Progress--support was always through the ERP vendor. If that vendor doesn't have a solution for a DB issue...

I just did my first ASP.net page that connects to our Progress back end. We had some trouble with locks a while back, so I decided to split out my reads and writes with separate DSNs. I've got a read only (Read Uncommitted) DSN, and a RW (Read Committed) DSN. Now, the real question I have is...

The error is generated at the data retrieval level, so nothing you can do on your code is going to make it go away, other than not returning the field that is bigger than it's stated ODBC size. We recently learned of dbtool, and I never would have imagined that fixing the issue was so simple...

I guess I must not have been clear--there's no errors. The PDF converter works exactly as designed. It's just that design that blows. Here's the entire process: User generates a report to View Report Manager (on Unix) picks up report and runs it Report Manager (somehow--still not sure...

We're now 5.5, and I believe it would be "outbound"--as in turning print to email and print to view report jobs into PDF. My understanding is that the PDF converter is basically the same (with a tweak made to the code for the 5.5 upgrade) since version 3 or 4.

Anyone use anything other than the Infor PDF Converter with SX (not sure if it's an option in character, but we're exclusively GUI)? I'm sick of the Infor PDF Converter. For a "free" addon, it cost us enough to get into place (they didn't tell us until during the install that we needed to...

We've begun using SQL Reporting Services as well; right now we're primarily using Brio (Hyperion, whatever it's called now) for reporting against the SX database. I'm hoping to get us using SQL much more heavily in the next 6 months, as we are site licensed for SQL. As for the data structure...

OK, had a brain fart when I started playing with this again. I always do a complete install of Client Networking, and the ODBC driver is always there on the 32 bit servers. I installed Client Networking probably 4 times on this box, and I did the exact same thing. And like I mentioned in the...

No love there. That one is definately the 32 bit version, as it does list more drivers than the default tool or the one in system32 that is supposedly 32 bit--but the OpenEdge driver is still not listed.

So, just so I know what I'm doing, after I truncate the BI this weekend, do I then run prostrct remove <dbname> bi and that's it? From what I can garner from the online documentation, do I probably need to feed it the extent name as well? I'm guessing I still need to do something to...

I haven't. I've played with it a little more since then, but the results have been the same--nothing I can do will make the ODBC driver show up in the 32 bit ODBC Manager.

Had our database shutdown in the middle of the night last night; our variable length BI extent filled up. Not sure if it was the right thing to do, but I just added another bi extent. I believe the problem was caused by a piece of code that we run quarterly; it is a big process, and this is...

No, it's not what you think--I do know how to start the 32 bit version of Data Sources Manager. The docs on the Progress Knowledgebase make things sound so simple--install the Client Networking portion of the client onto the 64 bit server, and then fire up the 32 bit version of the Data Sources...

Money is just a "thing"--IMO, happiness is more a factor of what you are *doing*, not what you have. Yes, having money can allow you to do things that can make you happy--but if you can live comfortably and do the things you want with $50,000 a year, how much happier can having $500,000 a year...

I'm active on a few forums (one quite large), but I ran across ProgressTalk while I was googling for some (*gasp*) stuff about Progress, and I figured I might as well check out a forum actually related to what I do, instead of forums dedicated to how I waste my time. :) So, by way of...