Normal Topic Lookup Problems (Read 444 times)
iannew
Member
*
Offline


No personal text

Posts: 2
Location: UK
Joined: Sep 14th, 2005
Lookup Problems
Sep 15th, 2005 at 12:25pm
Print Post Print Post  
I am a new Sesame user and in the process of translating numerous records from Q&A 4 for DOS to Sesame.

To avoid having to translate all the databases in one go I need to use @xlookup to get data from a Q&A 4 database (which has approx 38,000 records) into the new Sesame application.

It works but is extremely slow even when both the Q&A database and the Seame application are on the same hard drive.

Is there a way to speed up the lookups? 


  
Back to top
 
IP Logged
 
The Cow
YaBB Administrator
*****
Offline



Posts: 2530
Joined: Nov 22nd, 2002
Re: Lookup Problems
Reply #1 - Sep 15th, 2005 at 1:12pm
Print Post Print Post  
[quote author=iannew  link=1126787150/0#0 date=1126787150]I am a new Sesame user and in the process of translating numerous records from Q&A 4 for DOS to Sesame.

To avoid having to translate all the databases in one go I need to use @xlookup to get data from a Q&A 4 database (which has approx 38,000 records) into the new Sesame application.

It works but is extremely slow even when both the Q&A database and the Seame application are on the same hard drive.

Is there a way to speed up the lookups? 

[/quote]

When doing an XLookup to a .DTF file, Sesame must partially translate that Q&A file into something readable. It must do this for each XLookup because it does not know whether you intend to do more, or stop at one. Some applications do many XLookups from a small set of files, and others do a few XLookups from many files. I wish Q&A had implemented QABasic commands that indicate when the application wants external resources and (more importantly) when it is really actually done with them. Something like file open and close commands.

To speed this up, you could try translating the .DTF to a Sesame format. That will allow Sesame to load the file into memory for subsequent XLookups - speeding up all but the first one.

Also, having all files on a single harrdrive will actually slow down any program (not just Sesame) in that two hard drives can be nearly read simultaneously, but one hard drive can only be read sequentially.
  

Mark Lasersohn&&Programmer&&Lantica Software, LLC
Back to top
IP Logged