Thanks for the post and welcome.
You can search ("Find" actually...) any field you want, regardless of whether the data was autoentered or not.
Enter find mode (under the "View" menu)
type is your search criteria
hit the Enter Key.
Is this what you're looking for?
I have a customers table with a unique ID field "CustomersID".
and in the options tab Auto Enter I've selected Creation Date as an option.
this isn't a good way to have an unique ID.
In the option of auto-enter a value for the field: CustomerID, you have to set serial from 1 step 1, not mofifiable.
The option of auto-enter the creation date must be setted for ANOTHER field.
Unfortunately, the find does not return the record set I've searched for.
When I search for any date or date range in this field it returns all records in the table.
The field data type is text if that helps.
Thanks for your reply. Because I'm working from a pre-existing design I was just trying to figure a way to search without modifying the table. It sounds like that might be my only option.
Setting CustomerID to auto-enter the creation date is NOT an option... it is a deliberate way to kill your app.
1. searching for a date range in a field that is formatted to text is probably why a date range search is not working the way you want it to. If you want to search by date range, create ANOTHER FIELD that is also autoenter with date created and is in date format. Search that one.
2. raybaudi knows what she's talking about. While you know your application best, there are some actions that are inherently dangerous across the board. If you Autoenter record creation date, and make two records on the same day, your Unique Identifier is not so very unique, is it? That's what can kill your app.
raybaudi mentioned a serial# above...please consider this well, we all use it for a very, very good reason. In the end, the final call is yours.
FMP will let you do things that are against your best interests. Sure, they are an available option...but they aren't really an OPTION, so to speak.
Thanks again. I understand the design is flawed and will have to make adjustments to find the result I am after. My intention was to swim around for an answer within the context of my problem and not to make changes. Also, I didn't mean to imply that raybaudi didn't know of what she speaks just to point out that it was option. Thanks for the resolve.
It's been a pleasure :robothappy:
This picture shows only that a field can have more than an option for auto-enter a value...
but your CustomerID, as like any other ID, can have ONLY Serial checked to do what they are asked to do: work as the primary key for relationships.