Clipper.5.x/dbase III Combo

[jamk555]

I have taken over an application (interpret this as 'does not have source code') that was written in Clipper 5.x (from what I can gather). It is using a dbase III structured database.

I am running out of record space. I do not know if it is because of the application or dbase III. From what I can gather, dbase III is only limited by the file size.

My question is this - Should I attempt to decompile the source and see if the limitation is in the application? Or is there a way to convert the "backend" without modifying the clipper code?

I hope this is clear enough. Let me know if you have any questions.

Thanks.

Jason

 

[sduraiappan]

Use DBU and Reindex the appopriate index files.


Duraiappan.

 

[fmoore0001]

Here at Tasq, Inc. we are using something called the Advantage TPS RDD, actually kind of a client/server system. I am working with several tables OVER 10 gig (yes, 10 gig, no mistake) in size. It is easily the largest Clipper system I have every worked with, and I am inpressed to say the least.

I got this out of their *.NG file

Extended Systems Inc.
5777 N. Meeker Avenue
Boise, Idaho 83713
U.S.A.

Web Address:

http://www.advantagedatabase.com

Bulletin Board Service: 208-327-5020
Fax: 208-327-5006
CompuServe: 71003,3442 (Forum: GO EXTENDSYS)
E-mail: info@extendsys.com

Mailing Address: Extended Systems
Attn: Advantage Technical Support
5777 N. Meeker Avenue
Boise, Idaho 83713

 

[circes9]

what is the specific error you are getting?
dBaseIII has a limit to the number of records it allows in a database, I think its 1 million. Other xbase structures have ways around that limit; but to use another file type will require access to the source code.
Possibly the error is for a condition other than exceeding the maximum number of records, like memory or disk space.
Let us know

 

[jamk555]

All:

Thank you all for the help.

I do not have the source code - here's a little more detail -

The company that wrote the software has went out of business - I cannot even contact the person on his personal phone. All I have are some vague notes of different mundane tasks that I already knew. I cannot even figure his logic out based on the index keys. (it seems very inefficient, although they say if you program it right, you should not be able to troubleshoot it (hahaha))

We know that we are hitting the record limit. Right now, I do not have the exact error, I keep performing preventice maintenance before it occurs (have to keep the bosses happy). I will copy a backup and recreate it for you.

The current resolution is to purge records from the db from X date back. This allows it to run again. Sorry again for not having the error message.


I Attempted to update all of the NTX files with WinDBU (sp?). The App ran, however, when it performed its own reindexing, it reverted back. My assumption is the the application cannot handle a more current release.

I have 2GB Memory, with 70GB free (WIN2K SP3 NTFS). with autoexec.nt Files = 240

The system runs fine when it does not hit the limit.

I guess a better question is if a clipper 5.x application is performing the index, is there a way that I can force it to index with a "better" or updated version of Dbase without the source?

Again, thank you for the help.

 

[fmoore0001]

Thought of just getting the program decompiled if no one exists to help you on it?

 

[jamk555]

Ultimately I will propose that as one of the options in addtion to scraping the whole thing and hiring one of you guys.

I guess I am looking for the simplest solution (i.e. no learning curve for the end users)

Again, thank you to each of you(sduraiappan, fmoore0001, circes9).

 

[circes9]

Would your business allow for breaking out 'older' records from the more current ones? Is it required that ALL records be available IMMEDIATELY to users?

Consider multiple copies of your location. One location would be the 'archieve', and another your 2003 runtime area.

There are free utility programs where you could delete certain records for the file(s) and reduce their size, speed up its operation, and never have to touch the code.

If you think this is an option, let me know.

Circes

 

[RHankinsJr]

circes9 hit on a good point, you could have multiple copies of the program, this would allow you to strip out this years data and last years and so on. Just to keep the file size down... I do not know what kind of app it is so this is the best help I can offer.

Richard L. Hankins Jr.
Senior Programmer
Auction Services, Inc.