A Microsoft Office (Excel, Word) forum. OfficeFrustration

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

Go Back   Home » OfficeFrustration forum » Microsoft Access » Database Design
Site Map Home Register Authors List Search Today's Posts Mark Forums Read  

Form Design



 
 
Thread Tools Display Modes
  #1  
Old October 29th, 2009, 11:11 PM posted to microsoft.public.access.tablesdbdesign
dls61721
external usenet poster
 
Posts: 19
Default Form Design

I am using Access 2007. I have a db with 2 tables (employees, discipline).
The tables are not joined because i keep getting the error that there is a
mismatch in the data. There is a common field (employee #) in both tables. I
need to design a form that shows an employee and all the employee's
discipline. I'm really tired of going between the two tables to view
discipline on any given employee. Please assist.
  #2  
Old October 29th, 2009, 11:29 PM posted to microsoft.public.access.tablesdbdesign
Bernard Peek[_3_]
external usenet poster
 
Posts: 42
Default Form Design

In message ,
dls61721 writes
I am using Access 2007. I have a db with 2 tables (employees, discipline).
The tables are not joined because i keep getting the error that there is a
mismatch in the data. There is a common field (employee #) in both tables. I
need to design a form that shows an employee and all the employee's
discipline. I'm really tired of going between the two tables to view
discipline on any given employee. Please assist.


Open each table in design view and take a look at the employee# field in
each of them. Are they both numeric fields? If so are they the same type
of numeric field; integer, long integer etc?


--
Bernard Peek
  #3  
Old October 29th, 2009, 11:42 PM posted to microsoft.public.access.tablesdbdesign
KARL DEWEY
external usenet poster
 
Posts: 10,767
Default Form Design

First make sure the [employee #] field in both tables is the same data type.
Then run an 'Unmatched' query both ways - employees to discipline and
discipline to employees. Fix an records that do not match.
Make the [employee #] field of the employee table a primary key.
Create a relationship between the table selecting Referential Integrity and
Cascade Update.
Now you can use a form/subform for employee/discipline setting the
Master/Child links using the [employee #].
I recommend creating another table that is a list of all disciplines to use
instead of typing them in each time. Then you would use a combo box to
select the discipline being applied to the employee.

--
Build a little, test a little.


"dls61721" wrote:

I am using Access 2007. I have a db with 2 tables (employees, discipline).
The tables are not joined because i keep getting the error that there is a
mismatch in the data. There is a common field (employee #) in both tables. I
need to design a form that shows an employee and all the employee's
discipline. I'm really tired of going between the two tables to view
discipline on any given employee. Please assist.

  #4  
Old October 30th, 2009, 12:45 AM posted to microsoft.public.access.tablesdbdesign
John W. Vinson
external usenet poster
 
Posts: 18,261
Default Form Design

On Thu, 29 Oct 2009 15:11:01 -0700, dls61721
wrote:

I am using Access 2007. I have a db with 2 tables (employees, discipline).
The tables are not joined because i keep getting the error that there is a
mismatch in the data. There is a common field (employee #) in both tables. I
need to design a form that shows an employee and all the employee's
discipline. I'm really tired of going between the two tables to view
discipline on any given employee. Please assist.


Please post a description of your tables: fieldnames, datatypes, and whether
the field is a Lookup Field (it shouldn't be, see
http://www.mvps.org/access/lookupfields.htm for a critique of this
misfeature).

If each employee can be in several disciplines and each discipline can be
practiced by several employees, you need another table with the Employee# and
the DisciplineID.

--

John W. Vinson [MVP]
 




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Forum Jump


All times are GMT +1. The time now is 03:59 PM.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
Copyright ©2004-2024 OfficeFrustration.
The comments are property of their posters.