Re: Can Access use Fuzzy Logic

"kaniest" <kaniest@xxxxxxxxxxxxxxx> wrote

Larry Linson wrote
Just because you have some data stored, and in someone's view it
constitutes a "database" does not mean it is even one step along the
path from raw, random data to a relational database.

The validity of the data in a rdbms does not guarantee its
relevance. The merits of solutions to import problems
compare to the (busines) risk of errors - manual intervention,
missing accounts, offended customers, etc.
Consider James' remark on connecting data. Of course
it requires expertise and skill - and analysis. Access isn't
that different from other tools.

Are you saying "GIGO" in a lot of words? That's been a given, ever since the
computers I used were made with vacuum tubes.

"Relevance" of data was not the subject of this thread... but a specific
question about using databases, especially Access with "fuzzy logic" as a
solution to a particular problem posed by the original poster. "Fuzzy logic"
or "fuzzy matching" are not native features in Access and may, or may not,
be useful for the o.p.'s needs. Reminds me of some time I spent, about
twenty years ago, working with rule-based-systems in AI when all the pundits
predicted that the next year was going to be "the Year of Artificial
Intelligence", for several years running. None of those years actually was
"the Year of AI", and interest waned in the subject.

Access is, in fact, the UI and development tool. The actual database engine
can be the Jet database engine that comes with Access and is installed by
default, or you can use Access as a client to the heaviest-duty server DBs.
Access and whatever database engine you choose are a combination that is
quite different from some user's collection of directories, files, and
spreadsheets. And, so are a number of other databases.


.