Search results

yes i tried it with -cprcodein ISO8859-2 and -cprcodein UTF-8 it doesn't work with either of those @Cringer I already sent progress this example yesterday but i haven't got any answer yet

@RealHeavyDude: This works for me too, but when you compile this code as utf-8 and start it with a ISO8859-2 client, it doesn't work anymore..it just stops at the export statement... @Cringer: This works, but only as a workaround and i still don't understand why it won't work with export...

The problem is not that the delimiter is the wrong char, the problem is that when you use "~265" (or CHR(181)) as delimiter, progress exports nothing and doesn't raise an error message...and "~265" should be in every codepage (ISO8859-1 & ISO8859-2)

with the delimiter "~181" the file appears as "string1""string2" without any delimiter also with ~ you have to use the octal value and the octal value of 181 is 265

afaik you can't use CHR(x) or a variable as an export delimiter Edit: also with "µ" its the same problem

DEFINE VARIABLE giCount AS INTEGER NO-UNDO INIT 0. PROCEDURE CtrlFrame.PSTimer.Tick . /*------------------------------------------------------------------------------ Purpose: Löst das Event "PSTimerTick" aus, wenn der Timer abgelaufen ist. Parameters: None required for OCX...

chCtrlFrame:PSTimer:Interval = liSeconds * 1000.

ok....i know where the problem was.... .NET 2.0(?) is required for the silent installation i installed .NET 2.0 and it works now...

Hello, I create an ini file for my silent progress install. Here is my command line: C:\Progress1\Installations-CD\setup.exe -psc_s -psc_f1=C:\Progress1\Installations-CD\response.ini -psc_f2=c:\setup.log The response.ini was created automatically from an installation i performed with the...

We also started the progress session via scheduled task with a cmd-file where we first registered prox.dll with regsvr32 and than startet prowin32.exe. It doesn´t help, the warning somtimes occured (random?!?!). It also doesn´t matter if prox.dll is located on the network folder or on a local...

Warning: Prox.DLL is being used by another user. Please terminate the other process and try again. We use Progress V9.1D07 with Windows XPSP2! When does this warning generally appear? After confirming this message progress session starts and works fine. Our problem with this message is that we...

In procedure beginTransactionValidate I have to run some code if a field (LOGICAL) was set to true. If the BL returns that it is not allowed to set this field to true, an error sould occur and saving the record should be stopped (no problem with RETURN "<error-text>":U). But also the value of...

Thanks for your effort! I tried all possible mouse triggers but none fired! It seems that there is no way to recognize this!

Progress 9.1D07 (Windows XPSP2) I need to run some 4GL code when the window was moved with the mouse! Is there a way to recoginze this? Somthing like a END-MOVE-Trigger to the window would be great but doesn´t work! Thx!

I found my mistake! Bevor I dumped the database I had to correct the path of it and here I used a wrong structure file where I forgot the extent. So the information about the extent was lost and the data not dumped! Aaarrrr!

I have following problem: I had a db (2gb) with one extent (about 0,5gb). But I only wantet one db-file, so I created a new db and enabled the option "EnablelargeFiles" so that this db can get larger than 2gb. Than I dumped the db with the extent and loaded the data into the new db. Now it looks...

Is there a way to find out if "EnableLargeFiles" is activated with 4GL-Code? Maybe with the Virtual System Tables?

We have a single-select-browse widget and we want to recognize when "SHIFT + MOUSE-SELECT-CLICK" or "SHIFT + LEFT-MOUSE-CLICK" is pressed to run some special business logic. How is this possible? We use Progress V9.1D07 with Windows XPSP2! Thx!

I need to find out which index was used after "llOK = SUPER()." in function "openQuery" of a SDO! Can anyone help me?

With help from Progress Tech Support now I found my misunderstanding! I always thought that the updated and added records are wirtten to the db (in my case to the temp table) after running beginTransactionValidate. Then procedure endTransactionValidate is executed and after...