Execution Error 1

[tjbennett]

I am getting the following error after accessing the Extended Line Comments in P/O Multi-Level view:

Execution error: file 'INQPRGUP.LBR\POINQLIN.int'
error code: 153, pc=290A, call=39, seg=0

this error occurs every time:

Open P/O Multi-level view, enter item.
Click 'Open P/O'
Click on comments for the item.
Click Extended Line Comments.
Esc out of Extended Line comments
Esc out of P/O Line comments
Esc out of P/O line view
Execution Error 153

 

[dgillz]

Version of Macola? SQL or Pervasive and version info?

Does the PO in question actually have extended line comments?

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

http://www.gainfocus.biz

"If you have a big enough dictionary, just about everything is a word"
--Dave Barry

 

[MacolaHelp]

There were known issues in 76100a that caused 153 errors, for which I applied hot fixes. I still have those files but would need a way to transfer them to you if you can't get them off exact's website anymore.

 

[tjbennett]

We are running version 7.6.100a of Macola and Pervasive 2000i. It happens to all PO's, but the one I tested does have comments.

 

[MacolaHelp]

If you properly applied the hot fixes for 100a, your poprogup.lbr should be dated 10/25/02.

 

[tpllc]

There is a hot fix on the Exact site for this error.

Steve Henley
Trianglepartners.com
Exact Software consulting, sales and implementations.

If the only tool you can use is a hammer then all your problems look like nails.

 

[tjbennett]

Thanks MacolaHelp I checked the Macola WebSite and that hot fix is no longer available.

 

[tpllc]

Why are you still running code that is so far behind the current version? The current version is 7.6.400a. There are many reasons to stay current. If this is not an option I suggest that you contact your reseller or Exact direct and request the update the document number is 01.395.509. As long as you are current on your maintenance I'm sure they will get the update to. After all this is what you pay maintenence for If you have elected not to pay the maintenance then you are not entitled to the update.

Steve Henley
Trianglepartners.com
Exact Software consulting, sales and implementations.

If the only tool you can use is a hammer then all your problems look like nails.

 

[dgillz]

Actually my understanding is that due to legal issues regarding the switch from the Microfocus to the Fujitsu cobol compiler, no code or patch prior to 76200 is available from Exact.

You can get this from a reseller though.

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

http://www.gainfocus.biz

"If you have a big enough dictionary, just about everything is a word"
--Dave Barry

 

[tpllc]

I stand corrected. Don is right. There was a change in the licensing that Exact had with their compiller. Another strong reason that you should upgrade as these types of issue may occur again.

Thanks Don

Steve Henley
Trianglepartners.com
Exact Software consulting, sales and implementations.

If the only tool you can use is a hammer then all your problems look like nails.

 

[randva]

Mr. Henry:

Is "upgrading" the only tool you know how to use?

 

[tjbennett]

We do have 7.6.300 that I'm going to be upgrading to. I was just thinking of having a work around until I got it installed. Thanks.

 

[MacolaHelp]

tjbennett:

Upgrading will indeed fix the issue. If you still need the updated poprogup.lbr I can upload it to a public site for you to download. Post back if you need this done and I'll put it there until you can download it. If you've been on 76100a for a while, you must not have encountered a need to use extended po comments, otherwise you would have been looking for this fix a long time ago. It was a problem identified almost immediately in the 100a release. Good luck with the upgrade.

 

[tpllc]

Randva,
If you follow my posts you will see many other tips and suggestions when appropriate. I believe it is a waste of everyone’s time on this forum to try and answer why things don't work years after the software vendor has fixed a problem. ERP software is very complicated code and as such the vendor recognizes this and constantly provides fixes and enhancements in the new releases.
I recognize that new releases always introduce new problems as well as fixing old ones. That is why I never recommend upgrading just to upgrade. But there comes a time when you get too far behind. The original author of this post is at least 5 years behind the current code. As Don has stated there was a fundamental change that happened between 7.6.100 and 7.6.200. All software vendor stop supporting old code at some point in time as technology improves and resources are limited and better spent on improving the current code and new features.
I believe that this forum is also a resource that is better used to help people that help themselves.
Please do not take offence but you have hit a sore spot for me and I needed to get on my soapbox for a bit.


Steve Henley
Trianglepartners.com
Exact Software consulting, sales and implementations.

If the only tool you can use is a hammer then all your problems look like nails.

 

[MacolaHelp]

tjbennett et al:

This client is on pervasive 2000i & the last tested version of macola w/this database manager was 76300b. If any of my clients are still on pervasive 2000i, I don't have them go any higher on the code than 76300b, as they are truly adrift if things don't go right. For many small businesses, the decision to upgrade to a newer pervasive engine or convert to sql or replace with another software can be costly not only in software and conversion costs, but sometimes training as well. If their current software works or they can work around what problems they have encountered, it sometimes makes sense for them to just leave well enough alone. So I don't mind providing this fix if it is a show stopper for them, which I can't imagine it has suddenly become. Do they have custom source code enhancements or flex that should be considered in moving from 76100a?

That said, they should indeed move to 76300b and evaluate what the next step should be. I hope you have a reseller that you are working with to help you with the upgrade. Even going from 100a to 300b involves several steps and considerations that would be more efficiently done with an experienced reseller on hand.

All in all, 100a was a pretty solid release. If it's not broke, do we need to fix it other than the 153 error in PO currently?

 

[randva]

Mr. Henley:

Please accept my apologies.

My particular soap box involves people who only know one solution to a problem: upgrades.

Both of your replies addressed upgrades, combined with the line about hammers and nails -- well I just got carried away. It was inappropriate for this forum and so I apologize again.

Sincerely,
randva

 

[tjbennett]

Thank you for your help MacolaHelp. As you stated we are indeed a small business and as you said upgrading to the newer versions of Macola indeed is a cost matter that needs to be considered. What had happened is that our server crashed around January and had to be replaced and Macola/Pervasive had to be reloaded. We had many problems getting it running again without Macola crashing. We may have been on version 7.6.200 at the time of the crash, I can't remember but now that the 153 error is occurring it is time to update to the 7.6.300 version. I do have a reseller that I work with, however he has forgotten more about Pervasive (now that he pushes Macola ES) than I can remember. And I am afraid to touch Macola with all our problems of crashing we've had. Thanks again.

 

[tpllc]

Randva,
I'll try and not hammer the upgrade issue but I wonder how much has been spent in recovering their system now? Not only has the database become obsolete, their Progression code is not supported and the skill set of the market place has moved on as demonstrated in these many posting. The idea that small business can't afford to upgrade is in my opinion just the opposite, Small business can least afford to get too far behind. The annual spending on their system is more easily budgeted in small dosages rather than the catastrophic cost of recovery. We need to think of upgrading as preventative maintenance. Whether we like it or not technology is moving at an ever increasing rate, I never want to be on the bleeding edge or even the leading edge, but the cost of being left behind can be just as damaging.
I appreciate your apology but it is really not necessary the good thing about forums like this is everyone is entitled to their opinion.
Steve


Steve Henley
Trianglepartners.com
Exact Software consulting, sales and implementations.

If the only tool you can use is a hammer then all your problems look like nails.

 

[dgillz]

Steve is right on the money in regards to upgrades being preventative maintenance.

Having said that, the 153 error patch does work, I however like Macolahelp wonder why you are just now getting these errors.

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

http://www.gainfocus.biz

"If you have a big enough dictionary, just about everything is a word"
--Dave Barry

 

[MacolaHelp]

Did you buy a server that can run sql server and did you configure it according to macola specs? Do you have in house sql expertise or access to a db person to assist with installation, setup, configuring maintenance plans, etc? I would get your current macola version up to 76300b. If you can buy sql server for the server you have, I would then install sql server and convert from btrieve to sql. I always do 2 conversions: 1 to test and train, the second to go live. If clients have been on macola for a long time, I like to setup new users, screens, and forms in the target version. Why? Because they changed the code so much from 7x to 300b and the underlying files, form fields, etc., that I think it's more stable to redo those underlying structures than to let them convert with the original flaws still embedded. Once you convert to sql, you can then upgrade your macola to 76400a or higher if available. Then you are positioned properly for future progression updates or a migration to ES.

The btrieve to sql conversion is not cheap or quick if you have a lot of installed modules and do the due diligence on the testing before conversion. Upgrading to the newer pervasive database manager will be more economical to get you to current code. But, you will eventually need to go to sql if you want to migrate to ES. Of course, the more of the testing and configuring you do yourselves, the less in total it will cost.