OE2 tables

[AKPolarBear]

7.6.100a MSSQL

In our Data directory, I see some tables that are numbered OE2PO001 though OE2P0999.

Today, one of the users starting having a problem with a OEPO Generated OE. Started getting errors like SQL Open Failed ... OE2PO999 Table Not Found.

Another error read like:

SYS Error OE2PO999.BTR is not open

Not finding any other errors, I thought these might be similar to the .prt file that once they reach 99, you must delete the earlier ones in order to continue. That's what I did and was then able to access the particular OE's as needed.

And why did that second message call out a btr file extension when we are on SQL?

What are those files for and can they be deleted? They appear to be related to the OE to PO generation process.

 

[dgillz]

Using OE to PO under standard Macola 7.6.300 (I know you have modified source code) I amnot seeing any files like this created. What is the file extension? What does the OE setup file look like in regards to OE to PO options?

Software Sales, Training, Implementation and Support for Macola, eSynergy, and Crystal Reports

http://www.gainfocus.biz

 

[AKPolarBear]

These are tables found in the SQL data file.

We are using the Peak enhancement so the only set up I see is in the PDS file to generate immediate PO's from OE. The OE set up file has no reference to OE2PO generation.

 

[dgillz]

In 76300, OE to PO defaults are in OE setup, but are maintainable on an item-by-item basis.

Software Sales, Training, Implementation and Support for Macola, eSynergy, and Crystal Reports

http://www.gainfocus.biz

 

[TLeaders]

PolarBear

In Macola 7.6 any table can be a sql or btrieve table based on the entries a CFG file. I don't remember the name of the table, but support should be able to help you.

These files/tables are work files that are created (and Should be deleted) by the program or report that uses them, when the program finishes.

Just delete these btr files or drop the tables if sql, and your application should work fine.

I would also recommend that you report this error to Macola Support.

Good luck
Tom

 

[AKPolarBear]

Thanks for the advise, I will clear those out.

Past attempts to report errors like this to Macola have fallen on deaf ears with the usual response of "our records indicate that..." and to contact your VAR who will only charge a small fee to report a software bug on your behalf.

This is from the macsetup.cfg file:
[BTI Settings]
Server=NT
BtrvLocal=No
BtrvServer=Yes
SSQLLocal=Yes
SSQLServer=No
Check=Yes

 

[MacolaHelp]

You are on 7.6.100a, therefore you are using Peak's Best of OE, which generates exactly the type of file you describe. There are ddfs available for their files added, most of which begin with "oepds". The ddfs are included with the enhancement, you simply need to put them in the data folder. My most recent ddfs for Peak are dated 6/27/03. Macola has now taken over their code & starting with 7.6.300, the ddfs are not up to date, though since their acquisition of Tectura (formerly Peak's) client base, they claim to be in the process of updating vanilla macola ddfs.

For your immediate problem, the oe2po files are temporary placeholders created by the generate POs from OEs. These files can and should be deleted periodically. I imagine you have encountered the max number of any iteration of that file allowed. It's doing the same behavior as getting 99 of a spooled report or screen.tmp file.

 

[AKPolarBear]

I could not find any ddf files that begin with oepds. I did find 3 that are File,Index and Fields ddf's. The only other files found that begin with that are msl files.
I dug out the original installation disks and found nothing there as well.
Sounds like I might need a script to do some housecleaning.

 

[MacolaHelp]

Check the dates of your ddfs. When I downloaded peak's 100a enhancement, I got a zip file of their ddfs. I have gotten updates as well, so now my ddfs are 6.27.03. Additional peak tables are oepdsctl_sql, oepdshdr_sql, etc., which should be in EM or PCC if you have the correct ddfs installed. It sounds like your mssql install is trying to create or write to btr files? Have you checked the macola programs server to see if there are btr files in the data folder? If so, remove them.