General information
Category:
Databases,Tables, Views, Indexing and SQL syntax
Title:
Guarantee uniqueness in BROWSE?
Environment versions
Network:
Windows 2003 Server
I used to allow customers, when they logged single user, to change data in a simplistic BROWSE, where they could do some emergency changes.
I used to have just REGULAR indexes.
In forms I catch uniqueness violations with a VALID.
When I change an index to CANDIDATE now I don´t seem to be able to catch the global BROWSE error when uniqueness is violated by a key field being changed.
Do I need to generate a BROWSE FIELDS with a VALID clause for the unique field for every table in question now?
Thanks
G
Next
Reply
View the map of this thread
View the map of this thread starting from this message only
View all messages of this thread
View all messages of this thread starting from this message only