RE: [openroad-users] Open Road 5.1 question running the workbench directly from a start in directory

Allan Biggs

unread,

May 8, 2012, 3:50:10 AM5/8/12

to openroa...@googlegroups.com

Durwin,

This still doesn't run properly if I set the start in directory to 'our' start in directory it fails to find what I presume is an OR DLL when trying to debug our application .

If I set 'start in' to the ingres bin directory as an experiment the workbench debugger works but is obviously now in the incorrect start in directory so our application will not run. (the original reason for trying to run the workbench directly)

I am working in a virtual machine which doesn't have lotus notes or MS word loaded so the details of my reply are in the attached rtf file.

thanks

Allan

----- Original Message -----

From: Durwin Wright

Sent: 05/07/12 05:58 PM

To: Allan Biggs, openroa...@googlegroups.com

Subject: RE: [openroad-users] Open Road 5.1 question running the workbench directly
Hello Allan,

The problem is caused by the use of the double quotes for II_CONFIG. Try the following script,

set II_SYSTEM=C:\Program Files\Ingres\OpenROAD 5.1

set OR_SYSTEM=C:\Program Files\Ingres\OpenROAD 5.1\ingres\files

set II_CONFIG=C:\Program Files\Ingres\OpenROAD 5.1\ingres\files

set II_W4GLAPPS_SYS=C:\Program Files\Ingres\OpenROAD 5.1\ingres\w4glapps

for /f "tokens=*" %%J in ("%II_SYSTEM%") do set II_SYSTEM=%%~sJ

for /f "tokens=*" %%J in ("%OR_SYSTEM%") do set OR_SYSTEM=%%~sJ

for /f "tokens=*" %%J in ("%II_CONFIG%") do set II_CONFIG=%%~sJ

for /f "tokens=*" %%J in ("%II_W4GLAPPS_SYS%") do set II_W4GLAPPS_SYS=%%~sJ

::

::

::

::

PATH

ingprenv

::

::

"%II_SYSTEM%\ingres\bin\w4gldev.exe" runimage workbnch.img -cclassic -Tmin -L"%USERPROFILE%\appdev_5.1.log"

I removed the double quotes around the set commands for II_SYSTEM, OR_SYSTEM, II_CONFIG and II_W4GLAPPS_SYS and use the for statement to generate a short name. The short name does not require any double quotes to be used.

Let me know if you have any further problems.

Durwin Wright | Sr. Architect | Durwin...@actian.com | Actian Corporation | 500 Arguello Street | Suite 200 | Redwood City | CA | 94063 | USA +1 650-587-5523 | fax: +1 650-587-5550 | skype: durwin.wright | skype: +1 510-250-2524 | “Wag the Dog”

From: Bodo Bergmann
Sent: Monday, May 07, 2012 9:44 AM
To: Allan Biggs; openroa...@googlegroups.com; Durwin Wright
Subject: RE: [openroad-users] Open Road 5.1 question running the workbench directly

Do not include the double quotes in your SET commands.

From: Allan Biggs [mailto:all...@iname.com]
Sent: Monday, May 07, 2012 18:09
To: openroa...@googlegroups.com; Durwin Wright
Cc: Bodo Bergmann
Subject: RE: [openroad-users] Open Road 5.1 question running the workbench directly

Durwin,

This is the first time I have seen complex DOS commands - didn't know it was at all sophisticated - but give me VMS any day !!!

I got a bit lost but cobbled together this command file - which still fails

set II_SYSTEM="C:\Program Files\Ingres\OpenROAD 5.1"
set OR_SYSTEM="C:\Program Files\Ingres\OpenROAD 5.1\ingres\files"
set II_CONFIG="C:\Program Files\Ingres\OpenROAD 5.1\ingres\files"
set II_W4GLAPPS_SYS="C:\Program Files\Ingres\OpenROAD 5.1\ingres\w4glapps"
::
::
::
::
PATH
ingprenv
::
::
"C:\Program Files\Ingres\OpenROAD 5.1\ingres\bin\w4gldev.exe" runimage workbnch.img -cclassic -Tmin -L"%USERPROFILE%\appdev_5.1.log"

running this command file produced

c:\runw4gl>runopenroad.bat

c:\runw4gl>set II_SYSTEM="C:\Program Files\Ingres\OpenROAD 5.1"

c:\runw4gl>set OR_SYSTEM="C:\Program Files\Ingres\OpenROAD 5.1\ingres\files"

c:\runw4gl>set II_CONFIG="C:\Program Files\Ingres\OpenROAD 5.1\ingres\files"

c:\runw4gl>set II_W4GLAPPS_SYS="C:\Program Files\Ingres\OpenROAD 5.1\ingres\w4glapps"

c:\runw4gl>set OR_CONFIG_LONG=\

c:\runw4gl>PATH
PATH=C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;"C:\Program Files\Ingres\OpenROAD 5.1\ingres\bin"

c:\runw4gl>ingprenv
II_LANGUAGE=ENGLISH
II_TIMEZONE_NAME=GMT
TERM_INGRES=IBMPCD
II_INSTALLATION=XL
II_CHARSETXL=WIN1252
II_DATE_FORMAT=US
II_MONEY_FORMAT=L:$
II_TEMPORARY=C:\DOCUME~1\ALLUSE~1\OpenROAD\IngresXL\temp
II_CONFIG=C:\PROGRA~1\Ingres\OPENRO~1.1\ingres\files
II_GCNXL_LCL_VNODE=ALLAN-45F6ACB71
II_GCNXL_PORT=XL\NMSVR\7b4

c:\runw4gl>"C:\Program Files\Ingres\OpenROAD 5.1\ingres\bin\w4gldev.exe" runimage workbnch.img -cclassic -Tmin -L"C:\Documents and Settings\biggs2a\appdev_5.1.log"

the error log file appdev_5.1.log contains

ERROR: Could not open message file "C:\Program Files\Ingres\OpenROAD 5.1\ingres\files"\english\sw4gv4.mnx

sw4gv4.mnx is there but I notice in this error message that the full directory name is not formed correctly
it should be "C:\Program Files\Ingres\OpenROAD 5.1\ingres\files\english\sw4gv4.mnx"

I noticed this behaviour ( the " appearing immediately after \ingres\files ) when I tried
set OR_SYSTEM=%II_SYSTEM% as in your command file - this is why I used

set OR_SYSTEM="C:\Program Files\Ingres\OpenROAD 5.1\ingres\files"

Any ideas as to what is going wrong?

thanks
Allan
----- Original Message -----

From: Durwin Wright

Sent: 05/03/12 09:37 PM

To: openroa...@googlegroups.com

Subject: RE: [openroad-users] Open Road 5.1 question running the workbench directly but get error 8978462
Hello Allan,

This is probably my fault. I think you’re a looking at a bug in orwrap.exe. I will have to take a look at it this.

In the meanwhile, I have attached a zip file called evelop.zip that contains a file call develop.txt. This is actually a batch script called develop.bat that I use to launch workbench without orwrap.exe. We have a number of parallel OpenROAD build environments and I need to keep them separate.

It should answer any questions about how to launch workbench outside of orwrap.exe.

Durwin Wright | Sr. Architect | Durwin...@actian.com | Actian Corporation | 500 Arguello Street | Suite 200 | Redwood City | CA | 94063 | USA +1 650-587-5523 | fax: +1 650-587-5550 | skype: durwin.wright | skype: +1 510-250-2524 | “Wag the Dog”

From: openroa...@googlegroups.com [mailto:openroa...@googlegroups.com] On Behalf Of Allan Biggs
Sent: Wednesday, May 02, 2012 11:36 PM
To: openroa...@googlegroups.com
Subject: [openroad-users] Open Road 5.1 question running the workbench directly but get error 8978462

forgot to forward to the list -

I tried Bodo's suggestion but get error 8978462 with my attempts.

I am trying to emulate 4.1 behaviour where you have a start in directory can anyone point out where I am going wrong?

thanks
Allan
----- Original Message -----

From: Allan Biggs

Sent: 05/02/12 06:51 AM

To: Bodo.B...@actian.com

Subject: RE: [openroad-users] Open Road 5.1 question
Bodo,

Thanks I tried this but got errors - I think that I have tried all combinations and still get an error

>"C:\Program Files\Ingres\OpenROAD 5.1\ingres\bin\w4gldev.exe" "runimage" "workbnch.img" "-cclassic" "-Tmin" "-L" "%USERPROFILE%\appdev_5.1.log" >t.txt

It throws up W4GLDEV.EXE exiting , a trace window with nothing in it and this error text from the redirection

>type t.txt

ERlookup: Error accessing message text:

For unknown reasons.

Check messages files in the installation.

Internal error. Report this problem to your technical representative.

Ingres ERROR: 8978462

　

　

running

>"C:\Program Files\Ingres\OpenROAD 5.1\ingres\bin\w4gldev.exe" runimage "C:\Program Files\Ingres\OpenROAD 5.1\ingres\bin\workbnch.img" >t.txt

gives the same error

Can you suggest anything ?

best regards
Allan
----- Original Message -----

From: Bodo Bergmann

Sent: 04/25/12 08:45 AM

To: openroa...@googlegroups.com

Subject: RE: [openroad-users] Open Road 5.1 question
Hi Allen,

In OR5.1 the workbench shortcuts use a new utility called “orwrap.exe” to launch.

This wrapper extracts the II_SYSTEM, PATH etc. from the path of the utility (rather than the environment) and then launches it (from wherever it is located).

The orwrap utility is there to cater for multiple installations (with different II_SYSTEM, PATH, etc.), so you don’t have to switch environment variables.

So, the starting directory you specify in the shortcut is the starting directory of orwrap.exe rather than the one of the program (w4gldev.exe) launched.

In order to start w4gldev.exe from another starting directory you have to change the shortcut (or create a new one) to directly execute the workbench, e.g. using the following command:

w4gldev.exe runimage workbnch.img -/appflags faststart

Then it should work as in 4.1

HTH.

Regards,

Bodo.

From: openroa...@googlegroups.com [mailto:openroa...@googlegroups.com] On Behalf Of Allan Biggs
Sent: Wednesday, April 25, 2012 09:01
To: openroa...@googlegroups.com
Subject: [openroad-users] Open Road 5.1 question

We have just started to trial 5.1. initially on a clean windows XP installation.

I have set the 'start in' directory in the workbench short cut to point to the same folder that we use for 4.1. We have logos and our DLLs in this folder. When I run up our application under 5.1 it doesn't see the DLL. When I go through the motions of exporting a component the 'default' directory seems to be Ingres/bin.

Apologies I did find out how to do this , probably getting help from this list , when trying out the community edition mid last year but I cannot find any email referring to this.

thanks

Allan
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
This communication is for use by the intended recipient and contains
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
information that may be Privileged, confidential or copyrighted under
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
applicable law. If you are not the intended recipient, you are hereby
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
formally notified that any use, copying or distribution of this e-mail,
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
in whole or in part, is strictly prohibited. Please notify the sender by
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
return e-mail and delete this e-mail from your system. Unless explicitly
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
and conspicuously designated as "E-Contract Intended", this e-mail does
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
not constitute a contract offer, a contract amendment, or an acceptance
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
of a contract offer. This e-mail does not constitute a consent to the
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
use of sender's contact information for direct marketing purposes or for
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
transfers of data to third parties.
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
Francais Deutsch Italiano  Espanol  Portugues  Japanese  Chinese  Korean
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
           http://www.DuPont.com/corp/email_disclaimer.html
-- You received this message because you are subscribed to the Google Groups "OpenROAD Users Mailing List" group. To post to this group, send email to openroa...@googlegroups.com. To unsubscribe from this group, send email to openroad-user...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/openroad-users?hl=en.
-- You received this message because you are subscribed to the Google Groups "OpenROAD Users Mailing List" group. To post to this group, send email to openroa...@googlegroups.com. To unsubscribe from this group, send email to openroad-user...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/openroad-users?hl=en.
-- You received this message because you are subscribed to the Google Groups "OpenROAD Users Mailing List" group. To post to this group, send email to openroa...@googlegroups.com. To unsubscribe from this group, send email to openroad-user...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/openroad-users?hl=en.
-- You received this message because you are subscribed to the Google Groups "OpenROAD Users Mailing List" group. To post to this group, send email to openroa...@googlegroups.com. To unsubscribe from this group, send email to openroad-user...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/openroad-users?hl=en.
-- You received this message because you are subscribed to the Google Groups "OpenROAD Users Mailing List" group. To post to this group, send email to openroa...@googlegroups.com. To unsubscribe from this group, send email to openroad-user...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/openroad-users?hl=en.

orissues.rtf

Durwin Wright

unread,

May 8, 2012, 4:00:34 AM5/8/12

to openroa...@googlegroups.com

Hello Alan,

I forgot to have you set the PATH variable

. . .

set II_SYSTEM=C:\Program Files\Ingres\OpenROAD 5.1

set OR_SYSTEM=C:\Program Files\Ingres\OpenROAD 5.1\ingres\files

set II_CONFIG=C:\Program Files\Ingres\OpenROAD 5.1\ingres\files

set II_W4GLAPPS_SYS=C:\Program Files\Ingres\OpenROAD 5.1\ingres\w4glapps

for /f "tokens=*" %%J in ("%II_SYSTEM%") do set II_SYSTEM=%%~sJ

for /f "tokens=*" %%J in ("%OR_SYSTEM%") do set OR_SYSTEM=%%~sJ

for /f "tokens=*" %%J in ("%II_CONFIG%") do set II_CONFIG=%%~sJ

for /f "tokens=*" %%J in ("%II_W4GLAPPS_SYS%") do set II_W4GLAPPS_SYS=%%~sJ

set PATH=%II_SYSTEM%\ingres\bin;%II_SYSTEM%\ingres\utility;%PATH%

. . .

Add the line that is highlighted to your script. Do not put quotes around the PATH variable.

Bodo Bergmann

unread,

May 8, 2012, 4:03:13 AM5/8/12

to openroa...@googlegroups.com

Hi Allen,

OIEMBDNT.DLL is not part of OpenROAD 5.1 installation.

I think your problem is a wrong PATH setting, probably containing a PATH to an old Ingres/OpenROAD version.

Try setting the PATH in the batch script (after setting II_SYSTEM, but before running “w4gldev.exe”), e.g.:

SET PATH=%II_SYSTEM%\ingres\bin;%II_SYSTEM%\ingres\utility;%PATH%

You don’t have to use all the FOR statements in the batch script,

the environment variables are already set.

Keep it simple.

Bodo.

From: openroa...@googlegroups.com [mailto:openroa...@googlegroups.com] On Behalf Of Allan Biggs

Sent: Tuesday, May 08, 2012 09:50
To: openroa...@googlegroups.com

Subject: RE: [openroad-users] Open Road 5.1 question running the workbench directly from a start in directory

Allan Biggs

unread,

May 8, 2012, 6:34:13 AM5/8/12

to openroa...@googlegroups.com

Durwin,

I hard-wired the path after trying the mod to the script. Neither work it is still failing on OIEMBDNT.DLL . I was making an assumption the OIEMBDNT.DLL would have been required by the ORWRAP call or when the 'start in' directory is set to Ingres/bin but I guess in these circumstances because my code fails the OpenROAD debugger hasn't tried to call it.

I decided to look for OIEMBDNT.DLL which is in the ingres bin directory on my 4.1 installation. It does not seem to be present in the 5.1 installation that I have.

Any ideas have I missed some stage in the installation of 5.1 ? I only have OpenROAD on this PC there is no ingres installation.

Allan

this is the run

C:\amoss_testing>set II_SYSTEM=C:\Program Files\Ingres\OpenROAD 5.1

C:\amoss_testing>set OR_SYSTEM=C:\Program Files\Ingres\OpenROAD 5.1\ingres\files

C:\amoss_testing>set II_CONFIG=C:\Program Files\Ingres\OpenROAD 5.1\ingres\files

C:\amoss_testing>set II_W4GLAPPS_SYS=C:\Program Files\Ingres\OpenROAD 5.1\ingres\w4glapps

C:\amoss_testing>for /F "tokens=*" %J in ("C:\Program Files\Ingres\OpenROAD 5.1") do set II_SYSTEM=%~sJ

C:\amoss_testing>set II_SYSTEM=C:\PROGRA~1\Ingres\OPENRO~1.1

C:\amoss_testing>for /F "tokens=*" %J in ("C:\Program Files\Ingres\OpenROAD 5.1\ingres\files") do set OR_SYSTEM=%~sJ

C:\amoss_testing>set OR_SYSTEM=C:\PROGRA~1\Ingres\OPENRO~1.1\ingres\files

C:\amoss_testing>for /F "tokens=*" %J in ("C:\Program Files\Ingres\OpenROAD 5.1\ingres\files") do set II_CONFIG=%~sJ

C:\amoss_testing>set II_CONFIG=C:\PROGRA~1\Ingres\OPENRO~1.1\ingres\files

C:\amoss_testing>for /F "tokens=*" %J in ("C:\Program Files\Ingres\OpenROAD 5.1\ingres\w4glapps") do set II_W4GLAPPS_SYS=%~sJ

C:\amoss_testing>set II_W4GLAPPS_SYS=C:\PROGRA~1\Ingres\OPENRO~1.1\ingres\w4glapps

C:\amoss_testing>PATH
PATH=C:\Program Files\Ingres\OpenROAD 5.1\ingres\bin;C:\Program Files\Ingres\OpenROAD 5.1\ingres\utility;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem

C:\amoss_testing>ingprenv

II_LANGUAGE=ENGLISH
II_TIMEZONE_NAME=GMT
TERM_INGRES=IBMPCD
II_INSTALLATION=XL
II_CHARSETXL=WIN1252
II_DATE_FORMAT=US
II_MONEY_FORMAT=L:$
II_TEMPORARY=C:\DOCUME~1\ALLUSE~1\OpenROAD\IngresXL\temp
II_CONFIG=C:\PROGRA~1\Ingres\OPENRO~1.1\ingres\files
II_GCNXL_LCL_VNODE=ALLAN-45F6ACB71

II_GCNXL_PORT=XL\NMSVR\bcc

C:\amoss_testing>"C:\PROGRA~1\Ingres\OPENRO~1.1\ingres\bin\w4gldev.exe" runimage workbnch.img -cclassic -Tmin -L"C:\Documents and Settings\biggs2a\appdev_5.1.log"

----- Original Message -----

From: Durwin Wright

Sent: 05/08/12 09:00 AM

To: openroa...@googlegroups.com

Subject: RE: [openroad-users] Open Road 5.1 question running the workbench directly from a start in directory

Hello Alan,

I forgot to have you set the PATH variable

. . .

set II_SYSTEM=C:\Program Files\Ingres\OpenROAD 5.1

set OR_SYSTEM=C:\Program Files\Ingres\OpenROAD 5.1\ingres\files

set II_CONFIG=C:\Program Files\Ingres\OpenROAD 5.1\ingres\files

set II_W4GLAPPS_SYS=C:\Program Files\Ingres\OpenROAD 5.1\ingres\w4glapps

for /f "tokens=*" %%J in ("%II_SYSTEM%") do set II_SYSTEM=%%~sJ

for /f "tokens=*" %%J in ("%OR_SYSTEM%") do set OR_SYSTEM=%%~sJ

for /f "tokens=*" %%J in ("%II_CONFIG%") do set II_CONFIG=%%~sJ

for /f "tokens=*" %%J in ("%II_W4GLAPPS_SYS%") do set II_W4GLAPPS_SYS=%%~sJ

set PATH=%II_SYSTEM%\ingres\bin;%II_SYSTEM%\ingres\utility;%PATH%

. . .

Add the line that is highlighted to your script. Do not put quotes around the PATH variable.

Durwin Wright | Sr. Architect | Durwin...@actian.com | Actian Corporation | 500 Arguello Street | Suite 200 | Redwood City | CA | 94063 | USA +1 650-587-5523 | fax: +1 650-587-5550 | skype: durwin.wright | skype: +1 510-250-2524 | “Wag the Dog”

Bodo Bergmann

unread,

May 8, 2012, 7:49:39 AM5/8/12

to openroa...@googlegroups.com, Allan Biggs

Allen,

If I understand correctly, the error is not occurring when you start the workbench, but when you try to run/debug your application.

That has nothing to do with the OpenROAD installation.

It rather indicates a possible problem with your application.

Could it be that it is using 3GL procedures that does ESQL calls?

If that is the case, have you relinked the libraries (DLLs) using esqlc.lib (in %II_SYSTEM%\ingres\lib) rather than ingres.lib (from OR4.1)?

BTW:

As you haven’t installed into an existing Ingres installation, there should be a default Ingres/Net installation (II_INSTALLATION=XL).

You can check the following:

· The “Ingres Net XL” service should have been installed (Startup Type: Automatic) and should be running

· Open the “Net Client Command Window” from the “IngresàOpenROAD 5.1àOpenROAD Net Client” program group

o Enter the following command:
netexpress /check

o Use the terminal monitor to check your DBMS connection:
sql yournode::yourdb

Durwin Wright

unread,

May 8, 2012, 9:59:36 AM5/8/12

to openroa...@googlegroups.com, Allan Biggs

OIEMBDNT.DLL sounds like an Ingres 2.0 or Ingres 2.6 DLL reference. Ingres currently uses iilibembed.dll.

You should open an issue so that we can help you.

Allan Biggs

unread,

May 8, 2012, 11:03:31 AM5/8/12

to openroa...@googlegroups.com

Durwin/Bodo,

I suspect that Bodo is correct - I didn't interpret this as being the DLL that deals with "embedded" sql routines.

We do use embedded sql fortran in DLLs which makes it look as though the next stage is to re-create our DLLs under this later Ingres release.

I now need to find the install discs for the Compaq fortran compiler !!!

we are getting there

thanks
Allan

----- Original Message -----
From: Durwin Wright
Sent: 05/08/12 02:59 PM
To: openroa...@googlegroups.com
Subject: RE: [openroad-users] Open Road 5.1 question running the workbench directly from a start in directory

OIEMBDNT.DLL sounds like an Ingres 2.0 or Ingres 2.6 DLL reference. Ingres currently uses iilibembed.dll.
You should open an issue so that we can help you.

From: openroa...@googlegroups.com [mailto:openroa...@googlegroups.com] *On Behalf Of *Bodo Bergmann
*Sent:* Tuesday, May 08, 2012 4:50 AM
*To:* openroa...@googlegroups.com
*Cc:* Allan Biggs
*Subject:* RE: [openroad-users] Open Road 5.1 question running the workbench directly from a start in directory
Allen,
If I understand correctly, the error is not occurring when you start the workbench, but when you try to run/debug your application.
That has nothing to do with the OpenROAD installation.
It rather indicates a possible problem with your application.
Could it be that it is using 3GL procedures that does ESQL calls?
If that is the case, have you relinked the libraries (DLLs) using esqlc.lib (in %II_SYSTEM%\ingres\lib) rather than ingres.lib (from OR4.1)?
BTW:
As you haven’t installed into an existing Ingres installation, there should be a default Ingres/Net installation (II_INSTALLATION=XL).
You can check the following:
·The “Ingres Net XL” service should have been installed (Startup Type: Automatic) and should be running
·Open the “Net Client Command Window” from the “IngresàOpenROAD 5.1àOpenROAD Net Client” program group

oEnter the following command:
netexpress /check
oUse the terminal monitor to check your DBMS connection:

sql yournode::yourdb
HTH.
Regards,
Bodo.

From: Bodo Bergmann
*Sent:* Monday, May 07, 2012 9:44 AM
*To:* Allan Biggs; openroa...@googlegroups.com ; Durwin Wright
*Subject:* RE: [openroad-users] Open Road 5.1 question running the workbench directly
Do not include the double quotes in your SET commands.

From: openroa...@googlegroups.com [ openroa...@googlegroups.com ] *On Behalf Of *Allan Biggs
*Sent:* Wednesday, April 25, 2012 09:01
*To:* openroa...@googlegroups.com
*Subject:* [openroad-users] Open Road 5.1 question
We have just started to trial 5.1. initially on a clean windows XP installation.
I have set the 'start in' directory in the workbench short cut to point to the same folder that we use for 4.1. We have logos and our DLLs in this folder. When I run up our application under 5.1 it doesn't see the DLL. When I go through the motions of exporting a component the 'default' directory seems to be Ingres/bin.
Apologies I did find out how to do this , probably getting help from this list , when trying out the community edition mid last year but I cannot find any email referring to this.
thanks
Allan
This communication is for use by the intended recipient and contains
information that may be Privileged, confidential or copyrighted under
applicable law. If you are not the intended recipient, you are hereby
formally notified that any use, copying or distribution of this e-mail,
in whole or in part, is strictly prohibited. Please notify the sender by
return e-mail and delete this e-mail from your system. Unless explicitly
and conspicuously designated as "E-Contract Intended", this e-mail does
not constitute a contract offer, a contract amendment, or an acceptance
of a contract offer. This e-mail does not constitute a consent to the
use of sender's contact information for direct marketing purposes or for
transfers of data to third parties.
Francais Deutsch Italiano Espanol Portugues Japanese Chinese Korean
http://www.DuPont.com/corp/email_disclaimer.html

-- You received this message because you are subscribed to the Google Groups "OpenROAD Users Mailing List" group. To post to this group, send email to openroa...@googlegroups.com . To unsubscribe from this group, send email to openroad-user...@googlegroups.com . For more options, visit this group at http://groups.google.com/group/openroad-users?hl=en .

-- You received this message because you are subscribed to the Google Groups "OpenROAD Users Mailing List" group. To post to this group, send email to openroa...@googlegroups.com . To unsubscribe from this group, send email to openroad-user...@googlegroups.com . For more options, visit this group at http://groups.google.com/group/openroad-users?hl=en .
-- You received this message because you are subscribed to the Google Groups "OpenROAD Users Mailing List" group. To post to this group, send email to openroa...@googlegroups.com . To unsubscribe from this group, send email to openroad-user...@googlegroups.com . For more options, visit this group at http://groups.google.com/group/openroad-users?hl=en .

-- You received this message because you are subscribed to the Google Groups "OpenROAD Users Mailing List" group. To post to this group, send email to openroa...@googlegroups.com . To unsubscribe from this group, send email to openroad-user...@googlegroups.com . For more options, visit this group at http://groups.google.com/group/openroad-users?hl=en .

-- You received this message because you are subscribed to the Google Groups "OpenROAD Users Mailing List" group. To post to this group, send email to openroa...@googlegroups.com . To unsubscribe from this group, send email to openroad-user...@googlegroups.com . For more options, visit this group at http://groups.google.com/group/openroad-users?hl=en .
-- You received this message because you are subscribed to the Google Groups "OpenROAD Users Mailing List" group. To post to this group, send email to openroa...@googlegroups.com . To unsubscribe from this group, send email to openroad-user...@googlegroups.com . For more options, visit this group at http://groups.google.com/group/openroad-users?hl=en .

-- You received this message because you are subscribed to the Google Groups "OpenROAD Users Mailing List" group. To post to this group, send email to openroa...@googlegroups.com . To unsubscribe from this group, send email to openroad-user...@googlegroups.com . For more options, visit this group at http://groups.google.com/group/openroad-users?hl=en .
-- You received this message because you are subscribed to the Google Groups "OpenROAD Users Mailing List" group. To post to this group, send email to openroa...@googlegroups.com . To unsubscribe from this group, send email to openroad-user...@googlegroups.com . For more options, visit this group at http://groups.google.com/group/openroad-users?hl=en .

Robert Allely

unread,

May 8, 2012, 4:48:56 PM5/8/12

to openroa...@googlegroups.com

Could it be the real problem is that OpenROAD became a Microsoft application so many years ago?

(Just kidding)

Confidentiality/Privilege Notice:
This communication is confidential and may be legally privileged. If you are not the intended recipient please delete the message and notify the sender at Ports of Auckland Limited. Any use, disclosure, copying, distribution or retention of this communication is strictly prohibited.

Reply all

Reply to author

Forward