Search results

Hi , Here is a simple 4GL code you can use: def var l-file as char no-undo. system-dialog get-file l-file must-exist. Best regards, Gabor

Hi, There are two possibilities: No.1: If the variable length extent is not used then you should remove it before adding further extents. It is recommended to add a fixed and variable length extent in one step. No.2: If the variable length extent is used then Progress fixes its length...

Hi, I think you are using Progress Workgroup Server. As KBase 20831 says "Only the Enterprise Database Server license allows this feature. However, it does not prevent you from creating single-volume databases with different block sizes, as Progress provides the empty databases for each...

Hi, What is the block size of your original DB? You can check it in promon-> 7. Database Status Database block size (bytes): xxx Best regards, Gabor

Hi, That's correct. As written in Kbase 15340: "The Workgroup Database Server does not include spin locks and the asyncronous IO processes APW, AIW, and BIW. Associated parameters such as -spin, -pwscan, -pwwmax are not part of the product." Regards, Gabor

Hi, We could set up Intersolv ODBC driver many years ago. As I know MERANT (the merged Intersolv and MicroFocus company) has the ODBC driver you need. ODBC v3.1 was purchased separately for Progress V7.3 and 8.x. ODBC V3.1 connected via the Progress OIB/OID to interface with SQL-89...

Hi, The mentioned variables are set to: DLC={dlc-path} PROMSGS=%DLC%\PROMSGS PROCFG=%DLC%\PROGRESS.CFG PROOIBRK=%DLC%\BIN\OIBRKR32.EXE PROOIDRV=%DLC%\BIN\OIDRVR32.EXE PROSTARTUP=%DLC%\BIN\STARTUP.PF and check also your PATH, %DLC% and %DLC%\bin must be there. Regards, Gabor

Hi, What I can see here is the hostname is missing (after -H). In addition you can check the following environment variables which must be set: PROCFG PROMSGS PROSTARTUP DLC Regards, Gabor

Hi, I could not find a solution, you may download the latest version from Microsoft (or from www.eastmensoftware.com?). It might help. Regards, Gabor

Hi, KBase entry 19261 mentions similar problem on HP-UX. http://www.progress.com/services/support/cgi-bin/techweb-kbase.cgi/dispentry.p?kbid=19261 I suggest not to access directly to shared memory use remote client access instead of that (-H, -S, -N client parameters) Regards, Gabor

Hi, On the server side the easiest way to check your Progress version is to look into the log file. It has an entry like: 09:01:42 BROKER 0: PROGRESS Version 8.3B on AIX. (4234) On the client side you can test it - in your code using 'display PROVERSION' - or in your script you can use...

Hi, There is a program in Windows called 'Imaging for Windows'. It has ActiveX interface you can use to display and manipulate your images. Supported file types are .tiff .awd .bmp .jpg .pcx .xif .gif and .wif. File imgocxd.hlp describes its interface under Win98. Regards, Gabor

1423 error is usually caused by trying to connect to a database that is running a different version of Progress than the one you are using to access it. Can you check your settings? Regards, Gabor

Hi, Here is a very small example, where you can define your directory and object path : <pre> DEF VAR l-dir AS CHAR. DEF VAR l-nextfile AS CHAR. DEF STREAM l-stream. DEF VAR l-objpath AS CHAR. l-dir = "x:\source". l-objpath = "x:\obj". INPUT STREAM l-stream FROM OS-DIR( l-dir )...

There is a patch in 9.1B20 might solve your problem. Details you can find here: http://www.progress.com/patches/index.htm Regards, Gabor

Hi, Under UNIX you may use 'file' command. It returns different values for ascii and xcoded files. Regards, Gabor

Hi, You can find it on the WEB: http://www.progress.com/v9/documentation/start.htm and select Programming Handbook in 4GL Collection. (Chapter 8 describes it !) Regards, Gabor

Hi, I could not see serious problem, so I can recommend only the followings: 1. Check you PROPATH on you client side 2. Check you network traffic 3. You may use/test smaller network buffers (-Mm) 4. -B has no effect on clients side 5. Check/set you temporary directory (-T should point...

Hi, You can find them on http://www.progress.com/v9/documentation/start.htm Regards, Gabor

Hi, The DB server looks nice (except I could not see BIW process) so we can examine op. system and client side. op.system - what is # vmstat 5 output (or similar sar command)? - what is your block size of your file system/DB? - are you using multi-volume DB? clients - as I can...