Error to connect the server

M

Merme

New Member
Hi all,

Sorry for my english, i'll try to explain my problem with simple words :D

So like my database became too big, i've began to archive.

That works fine, after this i wanted to create a new database only for archives.

So i've created it, i've take model with our empty database.

I can managed it with database editor and it looks great.

My problem is, when i've to connect it through Mfg Pro, i've an error message.
Code: 
us/gp/gpbrqgen.p  is missing
Code: 
us/mfdpers.p is missing
I've this message when i use the windows client, when i'm connecting in the character mode, that's telling me that the language file is missing.

I think that this message 'is normal' because we 're using french language, but i don't know where to configure it.

Thanks a lot fr your help.


Ps : mfg Pro version 8.6E
progress version : 8.3B
 
Those programs should be in your PROPATH or their root should be in the PROPATH.

MFG/PRO very rarely runs a program directly, instead it uses a couple of include files that take a program name and then tries to find the compiled program in the directory "us/" + first-two-letters-of-the-program, so it would expect to find gpbrqgen.p as us/gp/gpbrqgen.r, for example.

So, if your system in installed in /data/mfgpro and your code is installed in /data/mfgpro/live then you would have a sub-directory called /data/mfgpro/live/us and a lot of sub-directories containing compiled code (programs).

You need to ensure that your PROPATH contains the directory containing the "us" sub-directory /data/mfgpro/live (in this example, your directory structure will be diferent of course). That way, Progress will look in the PROPATH and will try to find the sub-directory "us" and "us/gp" of a directory in the PROPATH and will try to find the program there.

On our system, those files are in the QAD directory /data/qad/eB2/us ... so I'd check where they are in the O/S first, then check that the PROPATH refers to the correct place.

The other reason might be that the programs aren't there in the first place, so just check that the programs are there.
 
Hi,

Thanks a lot for your respond.

In fact, my is problem is that Mfg Pro search a directory call "us" and here the good directory is " fr ".

Because all the programs he is looking for are in fr.

And i can't change it, because it works for the 2 other databases.

So i would like to change the directory that's is looking for, but i absolutly don't know there i can change this parameter.
 
You are right, of course, your programs should be in fr not us as MFG/PRO uses the language code for the directory name. "fr" is French so your code sits in fr/...

What has happened is that someone at QAD had hardcoded the program to look in usgp and us/ rather than fr/gp and fr.

A quick and easy fix might be to do the following:

Go into the operating system (Unix/Linux/Windows) and cd to where the programs are kept, then cd into the directory immediately above the fr directory.
Create a directory "us" and a directory "us/gp".
Copy the files you need from fr into us.

For example, if you were in Unix, you would do something like this:

cd wherever your fr directory is
cd ..
mkdir us
mkdir us/gp
cp fr/gp/gpbrqgen* us/gp/
cp fr/mfdpers* us/

If you want to make sure that everything is there, copy everything from your fr directory into your us directory and try starting up again.
 
Yes, it works now.

But i don't want to keep two different directory with the same files, it would be source of futur problems i think :awink:

To start a connexion to the server :
What do i need ?

I mean that for my other database, i've two files which are lauching with the shorcut.
The first one, producti.pf => where the parameter and the names of the databases are.
And the second one progress.svg => where all the client parameters are, like the propath.

And that's all.

So i don't understand why it's work for the two others, and not for the third one.

Can the parameter of language be include in the database ?
 
Check that the PROPATH in all the scripts is the same.

If you are using configuration .ini files, then check that the PROPATH is the same in all the files, or use the same INI files. Similarly, check that all the scripts are using the same configuration settings.

Where possible, use the same start-up directory and the same settings for all the scripts, just changing the database name.
 
To launch Mfg Pro, it use 2 files :
producti.pf and progress.svg

This is the producti.pf

Code: 
-db mfgarch -ld qaddb -H MEMETECGPA01 -S mfgarch -N TCP  -trig TRIGGERS
-db winarch -ld windb -H SERVERNAME -S winarch -N TCP
-db specarch -ld specif -H SERVERNAME -S specarch -N TCP
-db largoarch -ld largo -H SERVERNAME -S largoarch -N TCP  
-db mfghelp -ld qadhelp -H SERVERNAME -S mfghelp -N TCP
-db guifr -ld qadgui -H SERVERNAME -S gui -N TCP  
-db cfgfr -ld qadcf -H SERVERNAME -S cfg -N TCP  
-h 7 -E -d dmy -yy 1950 -Bt 350 -c 30 -D 100 -mmax 8192 -nb 200 -s 63 -p mf.p -pf mfglang.pf

And in the progress.SVG i've all the parameters like the size of the windows, the color and the PROPATH

This is a part of progress.SVG

Code: 
DLC=\\SERVERNAME\progress\83b\dlc
PROBUILD=\\SERVERNAME\progress\83b\dlc\PROBUILD
PROPATH=.,c:,c:\qadgui\fr,c:\qadgui,c:\QADGUI\IMAGES.PL,\\SERVERNAME\specifgui\fr\src,
[URL="file://\\SERVERNAME\specifgui"]\\SERVERNAME\specifgui[/URL],
[URL="file://\\SERVERNAME\MFGPRO\86E\webasto\atos"]\\SERVERNAME\MFGPRO\86E\webasto\atos[/URL],
\\SERVERNAME\MFGPRO\86E\webasto\webasto,
[URL="file://\\SERVERNAME\mfgpro\86e\epm51sp6\gui\fr\src,\\SERVERNAME\mfgpro\86e\epm51sp6gui\fr\xrc,"]\\SERVERNAME\mfgpro\86e\epm51sp6\gui\fr\src,\\SERVERNAME\mfgpro\86e\epm51sp6gui\fr\xrc,[/URL]
[URL="file://\\SERVERNAME\MFGPRO\86E\epm51sp6gui,"]\\SERVERNAME\MFGPRO\86E\epm51sp6gui,[/URL]
[URL="file://\\SERVERNAME\MFGPRO\86E\proplus\qadguifs"]\\SERVERNAME\MFGPRO\86E\proplus\qadguifs[/URL],
[URL="file://\\SERVERNAME\mfgpro\86e\qadguif\fr\src"]\\SERVERNAME\mfgpro\86e\qadguif\fr\src[/URL],
[URL="file://\\SERVERNAME\mfgpro\86e\qadguif\fr\xrc"]\\SERVERNAME\mfgpro\86e\qadguif\fr\xrc[/URL],
[URL="file://\\SERVERNAME\MFGPRO\86E\QADGUIF"]\\SERVERNAME\MFGPRO\86E\QADGUIF[/URL],
[URL="file://\\SERVERNAME\MFGPRO\86E\QADGUIF\fr\BBI,"]\\[COLOR=#000000]SERVERNAME[/COLOR]\MFGPRO\86E\QADGUIF\fr\BBI,[/URL]
c:\progress\83b\dlc\gui,
c:\progress\83b\dlc,
c:\progress\83b\dlc\bin,
\\SERVERNAME\mfgpro\86e\mfgntsvr\fr\src

And this is the 'direction' of the client's shortcut.

Code: 
\\SERVERNAME\progress\83B\DLC\bin\prowin32.exe -l 1000 -pf Producti.pf -pf mfglang.pf -ininame PROGRESS.SVG

And this is the mfglang.pf

Code: 
-cpstream ibm850
-cpinternal iso8859-1 
-cprcodein iso8859-1 
-cpcoll basic

So i think that Mfg Pro just use these files but i'm not absolutly sure.

Thanks a lot for your help.
 
What about the Startup Directory? Is this the same for both scripts?

Since your PROPATH begins ".", Progress might be looking in your startup directory for the files. If that is different, it might be looking somewhere else instead.

Other than that, it all looks fine.
 
You must log in or register to reply here.
Back
Top