Reply-To: erik.wachtmeester@bighole.iaf.nl
Ben Cavanagh wrote in a message to Ron Tuynman:
BC> Not exactly, what I thought is that DbSeek can seek for 2 fields
BC> condition. Like DbSeek ("JAN 97", "132") --> search for
BC> date = JAN 97 and no_mag = 132.
Make that dbseek( 'JAN 97 132' ) and it will work, assuming that your
'date'-field is exactly 6 chars long and no_mag is 5 chars with the number
adjusted to the right. dbseek() only accepts 1 parameter as a seek argument
(and
a 2nd logical to indicate if it's to be a softseek or not).
But the index you created (date + no_mag) is actually stored and used as 1
concatenated string, so that's no problem at all.
Although I would never index on a textfield containing 'JAN 97', 'APR 98',
etc.
At least I would store these fields as '199701' and '199804' to get the index
in
a proper order. And it's quite easy to write 2 little functions that convert
user input 'JAN 97' to '199701' and screen output '199701' to 'JAN 97'.
But why not just use date fields for these? A little conversion routine is
also
very easy to write, and using a well chosen epoch setting you won't have to
worry about the 2000-problem, even if you're only using 2 digits for the
year...
RT>> application. Considering Clipper is obsolete and Windows has the
RT>> future, I would advise you to put your money on Delphi...
BC> I like Delphi to program in Pascal for Windows, but for the
BC> database I'll get a used version of Clipper VO or Foxpro.
Check out the Apollo VCL for Delphi from SuccessWare (now Luxent)! A native
database driver for Delphi (it doesn't use ODBC) that's fully compatible with
their great SIx database driver for Clipper. And since it's downward
compatible
with FoxPro and Clipper databases and indexes, you can use it on your
xisting
data.
Regards,
Erik
---
---------------
* Origin: May it be on this earth? (2:283/7.2)
|