Date: prev next · Thread: first prev next last
2011 Archives by date, by thread · List index


Dave

On Thu, 2011-08-25 at 18:25 -0400, dave boland wrote: 

planas,

I suspect you are on to something here.  The error (detailed version)
is:

SQL Status: S0011
Error code: -170

Primary or unique constraint required on main table: "tEmployeeType" in
statement [ALTER TABLE "tMainTable" ADD  FOREIGN KEY ("EmployeeType")
REFERENCES "tEmployeeType" ("EmployeeType")]

It looks like the relationship system is trying to add a key to
tMainTable, but can't for some reason.

Dave,


You can manually insert the each column into main. Under TOOLS select
RELATIONSHIPS. On the selection menu add the tables. Then under TOOLS (I
believe) select ADD Relationship. You then select the two keys that are
related Main.EmployeesID and Employees.EmployeeID (the correct foreign
key in Main with the key field of the table you are linking) 

-- 
  dave boland
  dboland9@fastmail.fm

-- 
http://www.fastmail.fm - Does exactly what it says on the tin





-- 
Jay Lozier
jslozier@gmail.com

-- 
For unsubscribe instructions e-mail to: users+help@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/users/
All messages sent to this list will be publicly archived and cannot be deleted

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.