asked on Set Relation/Set skip
I have an issue with something that has worked many times before, but not so much now. I have a large database of uses of plants by native peoples of north america, 44,691 uses. (Database is online at naeb.brit.org if you'd like to see what it's like} It's native form is FoxPro. I got a request from some college kids in Oregon who want to do a virtual tour of useful trees on their college campus. I said I'd help. I got a list of all the tree species in the county in Oregon where the college is. 113 species. I put their names (latin binomials) in a small database, named MarionORTrees.dbf. The main listing of all the plants is titled bothitem.dbf Here's the list of commands I used. Sciname is the names of the species in Marion County. Synthname is the latin names of all the species in the database.
CLEAR
SELECT a
USE "d:\data files\databases\synth99\Ma
SELECT b
USE "d:\data files\databases\food\bothi
SET ORDER TO SYNTHNAME && SYNTHNAME
SELECT a
SET RELATION TO sciname INTO b
SET SKIP TO b
BROWSE FIELDS a.sciname,b.synthname,b.co
BROWSE LAST FOR b.synthname#" "
The last command should show all the relevant info for the items in the main database for trees in Marion County. But it doesn't. I have various outcomes, some really loony, none really right.
I'm using what I believe to be the latest version of Windows 10 Pro: Build 15063
Any suggestions?
CLEAR
SELECT a
USE "d:\data files\databases\synth99\Ma
SELECT b
USE "d:\data files\databases\food\bothi
SET ORDER TO SYNTHNAME && SYNTHNAME
SELECT a
SET RELATION TO sciname INTO b
SET SKIP TO b
BROWSE FIELDS a.sciname,b.synthname,b.co
BROWSE LAST FOR b.synthname#" "
The last command should show all the relevant info for the items in the main database for trees in Marion County. But it doesn't. I have various outcomes, some really loony, none really right.
I'm using what I believe to be the latest version of Windows 10 Pro: Build 15063
Any suggestions?
DatabasesWindows OSFoxPro
Last Comment
Pavel Celba
It was just incorrect question understanding maybe... Try the following:
BROWSE LAST FOR !EOF('b')
Another option would be to display results in two BROWSE windows.
BROWSE LAST FOR !EOF('b')
Another option would be to display results in two BROWSE windows.
If you just have problem to display the last BROWSE window with the format equal the previous BROWSE command then you should look at your resource file.
To obtain the resource file name look at SYS(2005). If you empty the resource file then it should start working again.
To obtain the resource file name look at SYS(2005). If you empty the resource file then it should start working again.
ASKER
The third time I set the problem up with 2 browse windows, it worked; not easily, but it did work. Got the results into an excel file and sent it on to the students in Oregon. Still puzzled why a technique I've used for years didn't work this time without a lot of fiddling around. Ordinarily, I set a relationship between the two files, set skip on, and open one browse window with all the information matching the smaller file. Then do with it whatever I want. No longer apparently. One day FoxPro is not going to work at all any more, and I'm going to mourn. Thank you pcelba. None of your other suggestions worked, but that one did. Thank you.
If the two BROWSE windows work then SET SKIP should also work.
If you would post some data sample then I could investigate more. Your code should work and I am sure the problem is at your side not at FoxPro side... This does not mean FoxPro is bug free.
To investigate more I would need to know several settings etc.:
SET EXACT
FoxPro version
Code page (both FoxPro and tables) and collation used at run-time and in indexes
The two tables structure (you may create it by LIST STRUCTURE TO FILE )
You should check the sizes of columns used in the relation, you should reindex your tables and you should better describe what means "it does not work". I don't know what the BROWSE shows or whether it even appears... EE allows to post images so you may create some hardcopy of your screen and tell what's wrong with it.
BTW, the build 15063 isn't the latest version but that's irrelevant in this case.
If you would post some data sample then I could investigate more. Your code should work and I am sure the problem is at your side not at FoxPro side... This does not mean FoxPro is bug free.
To investigate more I would need to know several settings etc.:
SET EXACT
FoxPro version
Code page (both FoxPro and tables) and collation used at run-time and in indexes
The two tables structure (you may create it by LIST STRUCTURE TO FILE )
You should check the sizes of columns used in the relation, you should reindex your tables and you should better describe what means "it does not work". I don't know what the BROWSE shows or whether it even appears... EE allows to post images so you may create some hardcopy of your screen and tell what's wrong with it.
BTW, the build 15063 isn't the latest version but that's irrelevant in this case.
ASKER
I have a busy day; I can't do this all today. I can say that the browse "did not work" several ways. First, I seemed to have a working one browse window with a query made from two data files (dbfs). However when I moved the cursor from one item to the next, lines wiggled, and disappeared. Never ever seen anything like that before. On other occasions, I'd get the first column (from the smaller file), and nothing at all from the larger file. It varied rather dramatically (randomly?) from one attempt to the next.
Not sure what a "code page" is. Please advise. I'll try to do the rest tomorrow.
Thanks for your help.
dm
Not sure what a "code page" is. Please advise. I'll try to do the rest tomorrow.
Thanks for your help.
dm
ASKER CERTIFIED SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER
I had already responded to this, but, it seems not to be here.
Many thanks to pcelba. The SELECT command worked beautifully, very clear, got everything in a few seconds.
CPBFD() = 0
CPCURRENT() = 1252
Regarding SET SKIP being "old fashioned." I started using FoxBase ca1985. I had been using dBASE, but I learned early on that, with data sets of a few thousand items, what dBASE took overnight to do, FoxBase could do in a few seconds. At the time, the software was produced by a group of kids in southern Ohio who actually answered the phone themselves when I needed help. The documentation was clear, and I used it to create a very elaborate data entry system for what was to become my database of 44,000+ uses of plants by native American people for drugs, foods, dyes, fibers, and, occasionally, "Others." As noted, to see the online version, try http://naeb.brit.org . The upshot of all this is that most of my experience with Fox* was done before most folks on Experts Exchange were born. That's my apology for being "old fashioned."
I deeply appreciate the expertise of folks here. Odd stuff ordinarily gets cleared up in a few minutes. Thanks to all of you. dan
Many thanks to pcelba. The SELECT command worked beautifully, very clear, got everything in a few seconds.
CPBFD() = 0
CPCURRENT() = 1252
Regarding SET SKIP being "old fashioned." I started using FoxBase ca1985. I had been using dBASE, but I learned early on that, with data sets of a few thousand items, what dBASE took overnight to do, FoxBase could do in a few seconds. At the time, the software was produced by a group of kids in southern Ohio who actually answered the phone themselves when I needed help. The documentation was clear, and I used it to create a very elaborate data entry system for what was to become my database of 44,000+ uses of plants by native American people for drugs, foods, dyes, fibers, and, occasionally, "Others." As noted, to see the online version, try http://naeb.brit.org . The upshot of all this is that most of my experience with Fox* was done before most folks on Experts Exchange were born. That's my apology for being "old fashioned."
I deeply appreciate the expertise of folks here. Odd stuff ordinarily gets cleared up in a few minutes. Thanks to all of you. dan
Yah... I still have dBase 2 on 8" diskette somewhere...
The problem with old fashioned commands is not our age but the fact these commands were loosely tested in the new VFP OO world so you may observe C000005 error easily when using them intensively and in combination with object elements.
Regards
Pavel
The problem with old fashioned commands is not our age but the fact these commands were loosely tested in the new VFP OO world so you may observe C000005 error easily when using them intensively and in combination with object elements.
Regards
Pavel
BROWSE FIELDS a.sciname,b.synthname,b.co
then it waits for BROWSE window closing
and then the next BROWSE (the last command) displays the data for given condition.
Use following command:
BROWSE FIELDS a.sciname,b.synthname,b.co