On Tue, 21 Apr 2009 21:21:26 -0400, SgtBob s...@cox.net wrote:
Obviously a sore point... sorry.
It's not really a sore point with me. I was just asking if there was a
more appropriate place for technical discussions like this.
--
Dennis Kowallek (LTools)
http://zippersoftware.com/ltools
Bob, I don't think anyone posting to this thread was upset. I thought
Dennis was expecting someone might complain that the subject is not
strictly about Legacy since you can't see the tables directly in
Legacy.
The IDIME heading in TblSX was always very confusing to me (What does
it have todo
On Wed, 22 Apr 2009 13:21:12 -0700, Richard Van Wasshnova
rfvanwasshn...@gmail.com wrote:
The IDIME heading in TblSX was always very confusing to me (What does
it have todo with a 10 cent coin?). Dennis' calling it ID of
Individual, marriage, event was very enlightening enough to make it
worth
:
From: Dennis M. Kowallek kowal...@iglou.com
Subject: Re: [LegacyUG] Legacy and Access
To: LegacyUserGroup@legacyfamilytree.com
Date: Monday, April 20, 2009, 5:02 AM
On Mon, 20 Apr 2009 6:48:42 -0400, SgtBob
s...@cox.net wrote:
is there any data written out that explains the
columnar
On Tue, 21 Apr 2009 14:35:47 -0400, SgtBob s...@cox.net wrote:
what do the first 3-4 columns of data in the tblSX and tblSR mean?
If you open the database in Design View, some of the columns have
annotations (not always up-to-date).
It might help me to work in Access on some errors I am trying
SgtBob wrote
Rich - I wanted to know what the various data in the columns represent.
I can figure out most of them, but what do the first 3-4 columns of
data in the tblSX and tblSR mean? I.e., what do the numbers in those
columns represent?
IDSX is an ID number for each entry in tblSX and
On Tue, 21 Apr 2009 20:04:39 +0100, Jenny M Benson
ge...@cedarbank.me.uk wrote:
IDIME is the Individual's RIN which allows the Source Detail to be
linked to the correct Individual.
It can be ... but it can be other things also. If it was always a
pointer to a RIN, the programmers would have
Dennis M. Kowallek wrote:
On Tue, 21 Apr 2009 20:04:39 +0100, Jenny M Benson
ge...@cedarbank.me.uk wrote:
IDIME is the Individual's RIN which allows the Source Detail to be
linked to the correct Individual.
It can be ... but it can be other things also. If it was always a
pointer to a RIN,
Dennis M. Kowallek wrote
I wonder if there is a better place to discuss these issues. We are
probably boring 99% of the LUGgers.
LUGgers who are not interested in this topic don't have to read this
thread. Apart from those for whom it has an interest now, there may be
others in future who
Dennis M. Kowallek wrote:
On Tue, 21 Apr 2009 20:04:39 +0100, Jenny M Benson
ge...@cedarbank.me.uk wrote:
IDIME is the Individual's RIN which allows the Source Detail to be
linked to the correct Individual.
It can be ... but it can be other things also. If it was always a
pointer to a RIN,
On Tue, 21 Apr 2009 20:28:58 +0100, Jenny M Benson
ge...@cedarbank.me.uk wrote:
LUGgers who are not interested in this topic don't have to read this
thread.
And that's as it should be. I just know that, in the past, discussions
that got quite technical have generated complaints from
On Tue, 21 Apr 2009 20:04:39 +0100, Jenny M Benson
ge...@cedarbank.me.uk wrote:
IDIME is the Individual's RIN which allows the Source Detail to be
linked to the correct Individual.
If I remember correctly, TYPE refers to the Event which is being Sourced
- 1 being Birth, for example.
If you
To: LegacyUserGroup@legacyfamilytree.com
Subject: Re: [LegacyUG] Legacy and Access
On Tue, 21 Apr 2009 20:28:58 +0100, Jenny M Benson
ge...@cedarbank.me.uk wrote:
LUGgers who are not interested in this topic don't have to read this
thread.
And that's as it should be. I just know that, in the past
M. Brenzel wrote:
We are not all at the same level of experience with Legacy, with computers,
or with other software. We all need to be tolerant of the questions and
answers on this list, as long as they are polite in nature. I am a software
tester by profession and can write my own database
Didn't mean to upset folks in asking about the Access data. I will review the
items under the design feature and see if I can figure out the data. I'm not
that familiar with all the nuances of Access, so I will study it and refrain
from asking more questions on this area. Obviously a sore
Since I have heard that Legacy and Access are intertwined, is there any data
written out that explains the columnar headings and their uses within the
various Access reports. I am particularly interested in the correlation of the
numbers noted in the columnar headings of 'SrcDetail',
On Mon, 20 Apr 2009 6:48:42 -0400, SgtBob s...@cox.net wrote:
is there any data written out that explains the columnar headings and their
uses within the various Access reports.
I don't know of anything public that goes into this detail.
I created a list of the various Legacy tables and
headings and their uses
within the various Access reports.'
Rich in LA CA
--- On Mon, 4/20/09, Dennis M. Kowallek kowal...@iglou.com wrote:
From: Dennis M. Kowallek kowal...@iglou.com
Subject: Re: [LegacyUG] Legacy and Access
To: LegacyUserGroup@legacyfamilytree.com
Date: Monday, April 20
I'd like to put together a Legacy News article
(http://www.legacynews.typepad.com) on the added benefits of using Access
with Legacy. Specifically, what are some things that you can do with Access
that Legacy, alone, cannot do?
If you have suggestions and would like to contribute, please use the
19 matches
Mail list logo
