Relationship problems not involving a fear of commitment

[sliptdisk]

All I want to do is collect some data from a couple of different tables, sum a few fields, and, print a report. Unfortunately, the individual who designed this thing used primary fields that contained null values (not to mention that the data types are mostly "text" when numbers would be more appropriate). This thing is locked at the home office and won't allow me to change primary fields. Is there anything I can do publish reports with data from linked tables? I've tried to establish relationships by dragging them, but, although I save them, don't appear when I reopen the relat'p window. Is that because of the null value?

 

[LarryDeLaruelle]

If you are working with linked tables and are not able to modify them you might try copying them to another location and making the mods necessary to allow you to create your report.

Larry De Laruelle
larry1de@yahoo.com

 

[sliptdisk]

Indeed, I did copy them, but, am still getting these recognition errors returned.

Dan

 

[MichaelRed]

Try placing the "relationships" in queries in your database, not in the relationships window. The queries may be a bit slower, but they should retain the "relationships", as they represent "joins" in the queries, not true relationships. Really, the major difference in the "Joins" in queries and true 'relationships' is that the 'realtionships' can/are used to enforce referential integrity, where the 'joins' in the queries do not.



MichaelRed
mred@duvallgroup.com
There is never time to do it right but there is always time to do it over

 

[Shep]

Dan - you can't have null values in a primary Key - Access don't allow it.
One thing to check though, I sometimes find that the Relationships window doesn't always show all relationships unless you actually tell it to.

Shep

 

[sliptdisk]

Hmmm...

Well, I did try just linking the tables within the query, and, that seemed to help, although it's not reporting the null field value.

Dan

 

[MichaelRed]

I don't know what you mean " ... not reporting the null value field value ... " In 'datgabase-ease', null means - well "null". It is more-or-less undefined or nothing, so "not reporting" nothing would generally be an O.K. situation (at least if you can ignore the grammer).

If you need additional help, 'we' need additional details of the problem.

MichaelRed
mred@duvallgroup.com
There is never time to do it right but there is always time to do it over