• Please review our updated Terms and Rules here

dBase III-Plus - Can Anybody Help Me with this Program?

Have you copied all the data files to a directory on a drive that matches what the original install had? IIRC, dBASE embedded links in the queries and joined tables based on path names. Moving a dBASE install to a different directory could result in not finding the required files.
Thanks krebizfan, yes, this is the diagnosis we are revealing withs the conversations here. We believe we're missing a ***.qry program file, needed to create queries, to allow the Query buttons in the Setup and Create menus to work. Possibly for the reasons you outlined above, this file was never copied when I transferred my database with - what I thought were - all my dBase program files to other diskettes.

Can you tell me how to create a ***.qry file for dBase? If not possible, can you send me a copy of one you're using in your dBase III-Plus program?
Thanks for your consideration!!

Paul
 
Thanks krebizfan, yes, this is the diagnosis we are revealing withs the conversations here. We believe we're missing a ***.qry program file, needed to create queries, to allow the Query buttons in the Setup and Create menus to work. Possibly for the reasons you outlined above, this file was never copied when I transferred my database with - what I thought were - all my dBase program files to other diskettes.

Can you tell me how to create a ***.qry file for dBase? If not possible, can you send me a copy of one you're using in your dBase III-Plus program?
Thanks for your consideration!!

Paul

I doubt any query file I might have would be helpful since it would be linked to database files I can not send you.
Have you checked the menus for any that mention Query? I remember it being easy to create a simple query with a field to point to the correct database. My memory isn't completely reliable and I don't have a dBASE III+ manual at hand to confirm.
 
I doubt any query file I might have would be helpful since it would be linked to database files I can not send you.
Have you checked the menus for any that mention Query? I remember it being easy to create a simple query with a field to point to the correct database. My memory isn't completely reliable and I don't have a dBASE III+ manual at hand to confirm.
Hi krebizfan,

I understand you can't send me a query file linked to your sensitive files, but can you create a .qry file by using a small set of very simple "dummy" database records and send that file to me? You could send it to me via this VCF thread, or I can send you my e-mail address, whatever you prefer. It would be a great help!!!

Yes, I've checked and tried Query buttons found in all of the dBase menus and after linking to my database, I still can't query using my fields, I cannot choose any field to start a query.

Yes, I remember too, it was so easy to create a query chain with my fields and select cases from my database, based on these queries, but for some reason I can't do that now, I don't have the .qry file I used, even though I copied the entire dBase III-Plus program to diskettes and even my old Bernoulli 90 MB disk, but I can't create a query chain with any of those copied versions. I even downloaded dBase III-Plus from a dBase site, and still cannot create a Query.

Why did Ashton-Tate make such a great product so difficult to use, given the precariousness of its .qry file???

Thank you krebizfan for your insights and for whatever you can do for me!

Sincerely,
Paul
 
So, to summarise, if you haven't copied your original queries over to your 'new' machine environment, you can't use them (!).

So, what you have to do, is to Create a new Query and define the fields and operators you wish to use.

Open your desired database you wish to run the query against.

Use the Create -> Query menu item.

The system should give the query a name (e.g. Q1.QRY).

You then need to specify each field name in turn, followed by an operator followed by a constant or an expression against the selected field.

Repeat the above for each desired database field you wish to include in the query.

You started on this journey back in post #12 where you got as far as specifying the database field - but you then stopped and gave up!

Don't forget to save your query when you have created it.

>>> Why did Ashton-Tate make such a great product so difficult to use, given the precariousness of its .qry file???

I don't think it is Ashton-Tate's fault that you didn't save and copy your query is it?

I suspect that what you were doing originally is opening an existing query and modifying the constant/expression field to achieve your desired searching goal. If you don't have you original query available, you have to create a new one from scratch, and those brain cells have died off since you did this many years ago.

Go back to your post #12 and create a new (but simple) query to start you off on your journey again...

Dave
 
In my archives, I found an installation of dBase III PLUS. It is simply a folder named 'DBASE' and it contains many files (no subfolders). I even see a query file named NOTPAID.QRY

On my host computer, I copied that DBASE folder into C:\DOSBOX (i.e. there is now a folder on my host named C:\DOSBOX\DBASE)

I started DOSBox, then mounted C:\DOSBOX as F: drive. I then changed to F: drive. I then changed into the DBASE folder, then executed DBASE.EXE

dBase III PLUS started and then I went into assist mode.

I then selected the database file that I wanted to use. {Set Up}{Database}{F:}{TRAVEL.DBF}

I then listed its records. {Retrieve}{List}{Execute the command}

As follows, I then created a query to list only the records where field FIRSTNAME contains "Eric".

1. {Create} on the menu bar, then {Query}, then {F:}
2. When prompted for the filename, I entered: ERIC
3. Presently {Field Name} is highlighted. I pressed [Enter] key. A list of field names appeared in a box to the right.
4. I choose {FIRSTNAME} then pressed {ENTER}.
5. Presently {Operator} is highlighted. I pressed [Enter] key. A list of operators appeared in a box to the right.
6. I choose {= Matches} then pressed {ENTER}.
7. Presently {Constant/Expression} is highlighted. I pressed [Enter] key. A small arrow appeared to the right of {Constant/Expression}.
8. I entered in: "Eric" (including the rabbit ears)
9. The query was built. I right-arrowed so that {Display} was selected, then pressed the [Enter] key. One record was displayed.
10. I right-arrowed to {Exit} and then choose {Save}

There is now a file named ERIC.QRY in the DBASE folder.

1700215193336.png
 
So, to summarise, if you haven't copied your original queries over to your 'new' machine environment, you can't use them (!).

So, what you have to do, is to Create a new Query and define the fields and operators you wish to use.

Open your desired database you wish to run the query against.

Use the Create -> Query menu item.

The system should give the query a name (e.g. Q1.QRY).

You then need to specify each field name in turn, followed by an operator followed by a constant or an expression against the selected field.

Repeat the above for each desired database field you wish to include in the query.

You started on this journey back in post #12 where you got as far as specifying the database field - but you then stopped and gave up!

Don't forget to save your query when you have created it.

>>> Why did Ashton-Tate make such a great product so difficult to use, given the precariousness of its .qry file???

I don't think it is Ashton-Tate's fault that you didn't save and copy your query is it?

I suspect that what you were doing originally is opening an existing query and modifying the constant/expression field to achieve your desired searching goal. If you don't have you original query available, you have to create a new one from scratch, and those brain cells have died off since you did this many years ago.

Go back to your post #12 and create a new (but simple) query to start you off on your journey again...

Dave
Hi Dave,

Thanks for your guidance, we'll see if it works. We already used the Query in the Create menu, we couldn't do anything, but we'll try it again as you outlined above. I will update you on our progress.

We are reviving a database I created in Guatemala (1988-1991), of all known documented murders, massacres, cadaver finds, tortures, etc. It will be used by the Forensic Anthropology Foundation of Guatemala (FAFG) to ID some of the 200,000 murdered civilians, victims of the country's civil war (1960-1996), and to achieve some form of justice. I'm donating the info to the FAFG, and it will become free to the public sometime late 2024.

Thanks so much!! If we have any more questions, we'll let you know.

Sincerely,

Paul
 
In my archives, I found an installation of dBase III PLUS. It is simply a folder named 'DBASE' and it contains many files (no subfolders). I even see a query file named NOTPAID.QRY

On my host computer, I copied that DBASE folder into C:\DOSBOX (i.e. there is now a folder on my host named C:\DOSBOX\DBASE)

I started DOSBox, then mounted C:\DOSBOX as F: drive. I then changed to F: drive. I then changed into the DBASE folder, then executed DBASE.EXE

dBase III PLUS started and then I went into assist mode.

I then selected the database file that I wanted to use. {Set Up}{Database}{F:}{TRAVEL.DBF}

I then listed its records. {Retrieve}{List}{Execute the command}

As follows, I then created a query to list only the records where field FIRSTNAME contains "Eric".

1. {Create} on the menu bar, then {Query}, then {F:}
2. When prompted for the filename, I entered: ERIC
3. Presently {Field Name} is highlighted. I pressed [Enter] key. A list of field names appeared in a box to the right.
4. I choose {FIRSTNAME} then pressed {ENTER}.
5. Presently {Operator} is highlighted. I pressed [Enter] key. A list of operators appeared in a box to the right.
6. I choose {= Matches} then pressed {ENTER}.
7. Presently {Constant/Expression} is highlighted. I pressed [Enter] key. A small arrow appeared to the right of {Constant/Expression}.
8. I entered in: "Eric" (including the rabbit ears)
9. The query was built. I right-arrowed so that {Display} was selected, then pressed the [Enter] key. One record was displayed.
10. I right-arrowed to {Exit} and then choose {Save}

There is now a file named ERIC.QRY in the DBASE folder.

View attachment 1268115
Hi modem7

Thanks for the "tutorial" as daver2 says! We will try this, seems to confirm what daver2 says, we'll see what happens and let you know!! If we have any questions, we'll also let you know. Thanks so much again!!

Paul
 
You should be able to cursor up and down the field list and hit <RETURN> to select the desired field. Of course, there may be an incompatibility in the use of the cursor codes between your DOSBox setup and what DBase is expecting.

Again, this is not A-T's fault...

Dave
 
We are reviving a database I created in Guatemala (1988-1991), of all known documented murders, massacres, cadaver finds, tortures, etc. It will be used by the Forensic Anthropology Foundation of Guatemala (FAFG) to ID some of the 200,000 murdered civilians, victims of the country's civil war (1960-1996), and to achieve some form of justice. I'm donating the info to the FAFG, and it will become free to the public sometime late 2024.
Are the existing queries important? Maybe FAFG are going to be creating their own queries.

( I see that the Microsoft Access 2010 on my Windows 10 computer happily imported a .DBF data file from my DBASE folder. I thought that dBase data import functionality may have been dropped earlier. )
 
You should be able to cursor up and down the field list and hit <RETURN> to select the desired field. Of course, there may be an incompatibility in the use of the cursor codes between your DOSBox setup and what DBase is expecting.

Again, this is not A-T's fault...

Dave

Are the existing queries important? Maybe FAFG are going to be creating their own queries.

( I see that the Microsoft Access 2010 on my Windows 10 computer happily imported a .DBF data file from my DBASE folder. I thought that dBase data import functionality may have been dropped earlier. )
Hi modem7,

We haven't made any queries for FAFG yet, they probably will use a different database program, one they're already using.

Can you readily query your database with Access 2010, without creating a QRY file?

Thanks,

Paul
 
Can you readily query your database with Access 2010, without creating a QRY file?
Yes.
Access stores everything to do with the database (data, queries, reports, etc.) in one file, e.g. MyComputers.mdb
To pass it all to someone else (who obviously, has Microsoft Access, of an appropriate version), I just send them the one file.

( FYI. When the MDB file is in use, a temporary file using the file extension of LDB, e.g. MyComputers.ldb is present for locking purposes. )
 
Yes.
Access stores everything to do with the database (data, queries, reports, etc.) in one file, e.g. MyComputers.mdb
To pass it all to someone else (who obviously, has Microsoft Access, of an appropriate version), I just send them the one file.

( FYI. When the MDB file is in use, a temporary file using the file extension of LDB, e.g. MyComputers.ldb is present for locking purposes. )
Hmmmmmm.... Maybe eventually, I'll give that a try if dBase III-Plus doesn't work out as well as I thought it would!
 
Hmmmmmm.... Maybe eventually, I'll give that a try if dBase III-Plus doesn't work out as well as I thought it would!
There is a learning curve of course, but it is easy to use (particularly the aspect of a graphical interface compared to the 80x24 character box that the DOS version of dBase uses.)

After sending the data to FAFG for whatever DBMS system they use, you could, on an as-needed frequency:
1. Locally, in your Access database, generate queries graphically; then
2. Verify the expected results from the query; then
3. View the SQL statement that Access uses for that query, then send the SQL statement to FAFG for them to add to their system.

Or maybe if they are familiar with Access, and the MDB file is small enough, just send them the updated MDB, pointing out the new queries.

A few paths.

Maybe the Windows version of dBase. Surely it can use/import the existing .QRY files (as well as the data), saving you having to regenerate old queries. Again, a learning curve there.
 
Back
Top