Simple select statement fails with 'Failed to enable constraints' error for non-null, unique values or foreign key constraints when:
1. There are no foreign key constraints defined
2. There are no non-unique values in PK fields
3. There are no null values
The following statement, when used in a select command, causes the behaviour noted below:
SelectSQL = "Select Doc.* From Doc,DocViewOK,Role"
Notes & Behaviours:
I have put in the name of one table (DocViewOK), just to see if listing a table name without using it causes an error. It seems that it does not.
However, when I add the table 'Role', again without using it, I get the failure. If I use a WHERE clause with a field in Role set to a value that DOES exist, I still get the failure. However, if I set the same Role field to a value that does NOT exist, I get NO error. It almost seems like there is some 'phantom relationship' at work.
## Deliverables
1) Complete and fully-functional working program(s) in executable form as well as complete source code of all work done.
2) Deliverables must be in ready-to-run condition, as follows (depending on the nature of the deliverables):
a) For web sites or other server-side deliverables intended to only ever exist in one place in the Buyer's environment--Deliverables must be installed by the Seller in ready-to-run condition in the Buyer's environment.
b) For all others including desktop software or software the buyer intends to distribute: A software installation package that will install the software in ready-to-run condition on the platform(s) specified in this bid request.
3) All deliverables will be considered "work made for hire" under U.S. Copyright law. Buyer will receive exclusive and complete copyrights to all work purchased. (No GPL, GNU, 3rd party components, etc. unless all copyright ramifications are explained AND AGREED TO by the buyer on the site per the coder's Seller Legal Agreement).
## Platform
Windows