I have inherited a Maxus collection database in dbTextworks v8.0 with some 18000 entries. It was compiled from a variety of other databases in different formats. It has a number of duplicate numbers, although these refer to different objects from different original databases. The original database is indicated by the use of the characters # $ or % in another field.

So.

1/. How do I search for duplicate numbers - for example the use of "!" in a Filemaker Pro field pulls up all entries that occur more than once. How can I do this in Maxus/InMagic/dbTexworks (I'm not even sure what to call it!)

2/. How can I search for any of the indicator characters - # $ % . I have tried using them with or without quotation marks to no avail. The characters are there, but the search comes back as no result.

Rob Pilgrim

Dr Rob Pilgrim
Collections Coordinator
Pioneer Settlement Museum
Swan Hill Victoria AUSTRALIA

This message has been edited. Last edited by: Robfuscate,

One way to find records with the same value in a field is to:

1. Create an empty copy of the textbase (File>New Textbase>Copy an Existing Textbase Structure).
2. Export all the records from your original textbase.
3. Import the records into your new, empty textbase, and on the Import Options dialog box, on the Add/Replace Options tab, select "Check for Matching Records", If Match is Found: Reject New Record, and select the field containing your numbers as the Incoming Records Must Match field.

This will result in an exception file including all the duplicate records. One record with each number will be imported.

If the other field including the indicator characters were a Code field, you could search for the punctuation characters. On a Query screen, if you press F3 in the query box for a Code field, you'll see punctuation characters in the Term index (which you can then paste into the query box to search for the value). You can change a field's type by choosing Maintain>Edit Textbase Structure from the menu, clicking the Edit Fields button, selecting the field in the list, then selecting the desired option from the Field Type drop-down list. When you OK your changes to the structure, the field will be reindexed, which can be a lengthy process.

This message has been edited. Last edited by: CDale,

Thanks CD,

I had tried the input - match records for another problem to be sorted, but there are so many other errors in the combined databases that the number of rejections exceeded the number of acceptances.

Still, that was two months ago, I now have a slightly better grasp of the program than when I first started and some of the other anomalies have been sorted out - so I'll give it another go.

As to the % # $ problem,

Your advice regarding changing the field type to code worked . So that's the biggest, most important part of the problem sorted.

Onward, ever onward,

Thanks again.

Rob

This message has been edited. Last edited by: Robfuscate,