Jump to content

Finding a string within another file


Matty

This topic is 7555 days old. Please don't post here. Open a new topic instead.

Recommended Posts

The solutions would be different according to which one of your fields would be at left side ?

Is this that you want to identify the "related match" from first to second db, or the contrary.

If you wanted to find all related matches from "6hoy" (Left side), a find would be all what you'd need IMO. Finding only the 2 or 3 characters would not be different I assume.

If you wanted to find all related matches from

Link to comment
Share on other sites

You could do it with some calculated fields but whether it is worthwhile depends on the maximum length of the strings in db 1. If they don't get much longer than about 20 characters then you can do it with a calculated key field formula like:

Middle(TextField,1,3)&"

Link to comment
Share on other sites

Sorry, I'd try to clarify too.

I'm not suggesting a loop through the related records. I'm rather proposing a loop that would set the current record as a Multi-Line key, suitable for a relationship.

I assumed this wouldn't be a calculated field but rather a global field.

The Precision number I suggested was also designed to give you this "match latitude" that you requested.

Let try to map it out a little. I didn't tried it though...

t_Field

g_FieldParsed

g_Precision

g_counter

g_Mkey

SetField[g_counter,0]

SetField[g_FieldParsed, t_Field]

Loop

endLoopIf[g_counter = Lenght(g_FieldParsed)-g_Precision]

SetField[g_counter,g_counter+1]

SetField[g_Mkey, g_Mkey&"

Link to comment
Share on other sites

This topic is 7555 days old. Please don't post here. Open a new topic instead.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.