[AccessD] Assistance

Charlotte Foust cfoust at infostatsystems.com
Wed Mar 1 12:04:22 CST 2006


Of course, you could be truly rigorous and insist that field names be
unique ... ;o>

Charlotte Foust


-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of John Colby
Sent: Wednesday, March 01, 2006 9:58 AM
To: 'Access Developers discussion and problem solving'
Subject: Re: [AccessD] Assistance


Lol, my feeling exactly.  Plus it is nice to just look at a field name
and know where it comes from. 


John W. Colby
www.ColbyConsulting.com 


-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Dan Waters
Sent: Wednesday, March 01, 2006 11:40 AM
To: 'Access Developers discussion and problem solving'
Subject: Re: [AccessD] Assistance

Gustav,

I usually don't argue in this list but now I have to.  Do you really
want one field in every table called ID?  Typing is easy!  Trying to
hunt down which of 50 fields all named ID is causing the problem sounds
like a good all-day exercise.

Dan 

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Gustav Brock
Sent: Wednesday, March 01, 2006 9:13 AM
To: accessd at databaseadvisors.com
Subject: Re: [AccessD] Assistance

Hi Dan

Actually you are denormalizing the naming of the database schema this
way ... ID is fine. Outside the table it is tblMyTable.ID. Access does
this for you automatically. Why having trouble with
tblMyTable.MyTableID? Too much typing.

Sorry, couldn't resist. Boring day here - and remember: Clients do lie.
"I'm are experiencing locked records but everyone else is locked out."
My colleague drives to the client just to spot a laptop with wireless
network. You have one guess: Was this machine logged in to the
application?"

/gustav


>>> dwaters at usinternet.com 01-03-2006 14:28 >>>
AND, the name of the autonumber field MUST be the same as the table
name.

For example, tblMyTable has a PK Autonumber of MyTableID.

It MUST be this way!

;-)

Dan 
 

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of John Colby
Sent: Tuesday, February 28, 2006 10:59 PM
To: 'Access Developers discussion and problem solving'
Subject: Re: [AccessD] Assistance

ROTFLMAO.

Some things are just worth doing, always. 

Because of my dictatorial methods I am able to just look at my tables
and see the relationships, know what tables a field is in etc.  Works
for me. Most of my subjects don't dare speak up anymore, knowing my "out
the door, without a parachute" mentality.

;-)

John W. Colby
www.ColbyConsulting.com 


-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Rocky Smolin
- Beach Access Software
Sent: Tuesday, February 28, 2006 11:15 PM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] Assistance

Well, thanks to you and your dictatorial methodology I find I am now
completely unable to create a new table without defining an autonumber
PK as the very first field.  With ID as the suffix of the field name.

Thanks a lot.

And I mean that.

Rocky


--
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com

--
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com

-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com



More information about the AccessD mailing list