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 » Using Forms
Site Map Home Register Authors List Search Today's Posts Mark Forums Read  

New records can't be seen



 
 
Thread Tools Display Modes
  #1  
Old August 14th, 2004, 02:17 AM
rleblanc
external usenet poster
 
Posts: n/a
Default New records can't be seen

I have a form which is used for data entry. It works fine for data entry,
that is, the data is stored in the appropriate tables. However, when I use
the same form to see data it will not allow me to see the newly entered
data. Also the 'go to the end of records' button on the bottom of the form
will not allow me to look at data after record 1770 even though there are
more than 1786 records in the database. Filtering by form will also not
allow me to see anything over record 1770. The data is in the tables. I can
open a table and see that the data is in fact present. Just the form won't
allow me to see new records above 1770.
This is Access 2002.

Any ideas why the form is not seeing new records? It can see all the older
records.

Help please?


  #2  
Old August 14th, 2004, 02:32 AM
'69 Camaro
external usenet poster
 
Posts: n/a
Default New records can't be seen

Check the Form's Record Source Property (on the Form Properties "Data" tab)
to see whether it is based upon a saved query whose criteria excludes your
newest records or whether there's a SQL statement that also excludes your
newest records.

If the Record Source Property isn't the culprit, look at the VBA code to
find a "Filter = ..." for this Form (the code doesn't actually have to be in
the Form's module, since your Form can be referenced elsewhere) somewhere
that has criteria that excludes your newest records, as well as a "FilterOn
= True" statement.

HTH.

Gunny

See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips.


"rleblanc" noone@somewhere wrote in message
...
I have a form which is used for data entry. It works fine for data entry,
that is, the data is stored in the appropriate tables. However, when I use
the same form to see data it will not allow me to see the newly entered
data. Also the 'go to the end of records' button on the bottom of the form
will not allow me to look at data after record 1770 even though there

are
more than 1786 records in the database. Filtering by form will also not
allow me to see anything over record 1770. The data is in the tables. I

can
open a table and see that the data is in fact present. Just the form won't
allow me to see new records above 1770.
This is Access 2002.

Any ideas why the form is not seeing new records? It can see all the older
records.

Help please?




  #3  
Old August 14th, 2004, 03:00 AM
rleblanc
external usenet poster
 
Posts: n/a
Default New records can't be seen

Data Entry is set to no.

Record Source is set to SELECT. There are no VBA modules in this database as
yet.

If I set the Record Source to "client" (which is the master table to which
everything else is related), some of the fields get filled with #name?
instead of the actual data. However, the data in the client table is
completely accessible.

Any more ideas?

"'69 Camaro" wrote in message
...
Check the Form's Record Source Property (on the Form Properties "Data"

tab)
to see whether it is based upon a saved query whose criteria excludes your
newest records or whether there's a SQL statement that also excludes your
newest records.

If the Record Source Property isn't the culprit, look at the VBA code to
find a "Filter = ..." for this Form (the code doesn't actually have to be

in
the Form's module, since your Form can be referenced elsewhere) somewhere
that has criteria that excludes your newest records, as well as a

"FilterOn
= True" statement.

HTH.

Gunny

See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips.


"rleblanc" noone@somewhere wrote in message
...
I have a form which is used for data entry. It works fine for data

entry,
that is, the data is stored in the appropriate tables. However, when I

use
the same form to see data it will not allow me to see the newly entered
data. Also the 'go to the end of records' button on the bottom of the

form
will not allow me to look at data after record 1770 even though there

are
more than 1786 records in the database. Filtering by form will also not
allow me to see anything over record 1770. The data is in the tables. I

can
open a table and see that the data is in fact present. Just the form

won't
allow me to see new records above 1770.
This is Access 2002.

Any ideas why the form is not seeing new records? It can see all the

older
records.

Help please?






  #4  
Old August 14th, 2004, 03:32 AM
'69 Camaro
external usenet poster
 
Posts: n/a
Default New records can't be seen

Excellent. Open the Form in "Design View." Open the Properties window, and
select the "Data" tab. Place your cursor in the "Record Source" text area,
right in the part that reads "SELECT" and then press SHIFTF2 to open the
Zoom window. Copy and paste the entire SQL statement displayed in the Zoom
window into your next post so that we may see it and analyze it to determine
what's limiting your records.

By the way, when you make the "client" table the record source for your
Form, you're getting the "#Name?" showing in the text boxes on the form that
are bound to the fields in the one or more other tables in the query. Since
these fields don't exist in the "client" table, Access can't figure out what
field you want to bind each of these text boxes to.

HTH.

Gunny

See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips.


"rleblanc" noone@somewhere wrote in message
...
Data Entry is set to no.

Record Source is set to SELECT. There are no VBA modules in this database

as
yet.

If I set the Record Source to "client" (which is the master table to which
everything else is related), some of the fields get filled with #name?
instead of the actual data. However, the data in the client table is
completely accessible.

Any more ideas?

"'69 Camaro" wrote in message
...
Check the Form's Record Source Property (on the Form Properties "Data"

tab)
to see whether it is based upon a saved query whose criteria excludes

your
newest records or whether there's a SQL statement that also excludes

your
newest records.

If the Record Source Property isn't the culprit, look at the VBA code to
find a "Filter = ..." for this Form (the code doesn't actually have to

be
in
the Form's module, since your Form can be referenced elsewhere)

somewhere
that has criteria that excludes your newest records, as well as a

"FilterOn
= True" statement.

HTH.

Gunny

See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips.


"rleblanc" noone@somewhere wrote in message
...
I have a form which is used for data entry. It works fine for data

entry,
that is, the data is stored in the appropriate tables. However, when I

use
the same form to see data it will not allow me to see the newly

entered
data. Also the 'go to the end of records' button on the bottom of the

form
will not allow me to look at data after record 1770 even though

there
are
more than 1786 records in the database. Filtering by form will also

not
allow me to see anything over record 1770. The data is in the tables.

I
can
open a table and see that the data is in fact present. Just the form

won't
allow me to see new records above 1770.
This is Access 2002.

Any ideas why the form is not seeing new records? It can see all the

older
records.

Help please?








  #5  
Old August 14th, 2004, 03:59 AM
rleblanc
external usenet poster
 
Posts: n/a
Default New records can't be seen

The complete SQL statement is as follows:

SELECT client.MasterID, client.CreationDate, client.l_name, client.f_name,
client.MI, client.SSN, client.DOB, client.Street, client.City, client.State,
client.ZipCode, client.PhoneNumber, client.MaritalStatus, client.AdultDeps,
client.Children, client.Seniors, finances.ClientWages,
finances.UnemployComp, finances.WorkersComp, finances.TANF,
finances.SSDisability, finances.SSI, finances.VeteranPension,
finances.SSRetirement, finances.ChildSupport, finances.SSSurvivor,
finances.RentalIncome, finances.FoodStamps, finances.OtherIncome,
finances.WIC, finances.RentAssistance, finances.FuelAssistance,
finances.CityWelfare, finances.TEFAPLetter, finances.IncomeMemo,
misc.[General Memo] FROM (client INNER JOIN misc ON
client.MasterID=misc.MasterID) INNER JOIN finances ON
client.MasterID=finances.MasterID;


"'69 Camaro" wrote in message
...
Excellent. Open the Form in "Design View." Open the Properties window,

and
select the "Data" tab. Place your cursor in the "Record Source" text

area,
right in the part that reads "SELECT" and then press SHIFTF2 to open

the
Zoom window. Copy and paste the entire SQL statement displayed in the

Zoom
window into your next post so that we may see it and analyze it to

determine
what's limiting your records.

By the way, when you make the "client" table the record source for your
Form, you're getting the "#Name?" showing in the text boxes on the form

that
are bound to the fields in the one or more other tables in the query.

Since
these fields don't exist in the "client" table, Access can't figure out

what
field you want to bind each of these text boxes to.

HTH.

Gunny

See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips.


"rleblanc" noone@somewhere wrote in message
...
Data Entry is set to no.

Record Source is set to SELECT. There are no VBA modules in this

database
as
yet.

If I set the Record Source to "client" (which is the master table to

which
everything else is related), some of the fields get filled with #name?
instead of the actual data. However, the data in the client table is
completely accessible.

Any more ideas?

"'69 Camaro" wrote in message
...
Check the Form's Record Source Property (on the Form Properties "Data"

tab)
to see whether it is based upon a saved query whose criteria excludes

your
newest records or whether there's a SQL statement that also excludes

your
newest records.

If the Record Source Property isn't the culprit, look at the VBA code

to
find a "Filter = ..." for this Form (the code doesn't actually have to

be
in
the Form's module, since your Form can be referenced elsewhere)

somewhere
that has criteria that excludes your newest records, as well as a

"FilterOn
= True" statement.

HTH.

Gunny

See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips.


"rleblanc" noone@somewhere wrote in message
...
I have a form which is used for data entry. It works fine for data

entry,
that is, the data is stored in the appropriate tables. However, when

I
use
the same form to see data it will not allow me to see the newly

entered
data. Also the 'go to the end of records' button on the bottom of

the
form
will not allow me to look at data after record 1770 even though

there
are
more than 1786 records in the database. Filtering by form will also

not
allow me to see anything over record 1770. The data is in the

tables.
I
can
open a table and see that the data is in fact present. Just the form

won't
allow me to see new records above 1770.
This is Access 2002.

Any ideas why the form is not seeing new records? It can see all the

older
records.

Help please?










  #6  
Old August 14th, 2004, 05:00 AM
'69 Camaro
external usenet poster
 
Posts: n/a
Default New records can't be seen

Your query here is matching records in the "client" table with the records
in "misc" and "finances." There are 16 records in the "client" table that
have values in the MasterID field that have no matched records in one -- or
both -- of the other two tables. That's why these 16 records aren't showing
up in the Recordset that is being used as the source of your Form.

You need to determine whether these 16 records should or shouldn't be
included in the Form's Recordset, but first you need to see *which* records
are in the "client" table, but not in the other two tables.

To do so, create a new query. Paste this entire SQL statement into the SQL
View pane:

SELECT Client.MasterID, Misc.MasterID, Finances.MasterID
FROM (Client LEFT JOIN Misc ON Client.MasterID = Misc.MasterID) LEFT JOIN
Finances ON Client.MasterID = Finances.MasterID
WHERE (IsNull(Misc.MasterID) OR IsNull(Finances.MasterID));

Run the query. In the Client.MasterID field you'll see which 16 unmatched
records aren't showing up on your Form when you open it. Wherever you see a
blank in the field named Misc.MasterID or Finances.MasterID is where there's
a record that *might* be missing from one of these other tables. I write
"might" because there may be a good reason that these records don't exist in
these tables, but only you can decide that after you've gathered a little
more information.

Open the "client" table and search for the values in each of the 16 records
in the Client.MasterID field of the query you just created. Look at these
records and investigate why you may or may not need matching records in the
"misc" or "finances" tables.

If there *should be* matching records in each of these 16 cases, then you
need to figure out why they aren't there. Perhaps someone forgot to add
these records in other data entry Forms. Perhaps these tables are results
of imports from a spreadsheet or another database that never needed any of
these 16 records. Or maybe there are other reasons.

So, you need to do some further investigation, but at least you know *why*
those records aren't showing up in your Form, and you know exactly which 16
records are in your "client" table, but aren't in either of the "misc" or
"finances" tables.

Good luck and post back if you have any further problems.

HTH.

Gunny

See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips.


"rleblanc" noone@somewhere wrote in message
...
The complete SQL statement is as follows:

SELECT client.MasterID, client.CreationDate, client.l_name, client.f_name,
client.MI, client.SSN, client.DOB, client.Street, client.City,

client.State,
client.ZipCode, client.PhoneNumber, client.MaritalStatus,

client.AdultDeps,
client.Children, client.Seniors, finances.ClientWages,
finances.UnemployComp, finances.WorkersComp, finances.TANF,
finances.SSDisability, finances.SSI, finances.VeteranPension,
finances.SSRetirement, finances.ChildSupport, finances.SSSurvivor,
finances.RentalIncome, finances.FoodStamps, finances.OtherIncome,
finances.WIC, finances.RentAssistance, finances.FuelAssistance,
finances.CityWelfare, finances.TEFAPLetter, finances.IncomeMemo,
misc.[General Memo] FROM (client INNER JOIN misc ON
client.MasterID=misc.MasterID) INNER JOIN finances ON
client.MasterID=finances.MasterID;


"'69 Camaro" wrote in message
...
Excellent. Open the Form in "Design View." Open the Properties window,

and
select the "Data" tab. Place your cursor in the "Record Source" text

area,
right in the part that reads "SELECT" and then press SHIFTF2 to open

the
Zoom window. Copy and paste the entire SQL statement displayed in the

Zoom
window into your next post so that we may see it and analyze it to

determine
what's limiting your records.

By the way, when you make the "client" table the record source for your
Form, you're getting the "#Name?" showing in the text boxes on the form

that
are bound to the fields in the one or more other tables in the query.

Since
these fields don't exist in the "client" table, Access can't figure out

what
field you want to bind each of these text boxes to.

HTH.

Gunny

See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips.


"rleblanc" noone@somewhere wrote in message
...
Data Entry is set to no.

Record Source is set to SELECT. There are no VBA modules in this

database
as
yet.

If I set the Record Source to "client" (which is the master table to

which
everything else is related), some of the fields get filled with #name?
instead of the actual data. However, the data in the client table is
completely accessible.

Any more ideas?

"'69 Camaro" wrote in message
...
Check the Form's Record Source Property (on the Form Properties

"Data"
tab)
to see whether it is based upon a saved query whose criteria

excludes
your
newest records or whether there's a SQL statement that also excludes

your
newest records.

If the Record Source Property isn't the culprit, look at the VBA

code
to
find a "Filter = ..." for this Form (the code doesn't actually have

to
be
in
the Form's module, since your Form can be referenced elsewhere)

somewhere
that has criteria that excludes your newest records, as well as a
"FilterOn
= True" statement.

HTH.

Gunny

See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips.


"rleblanc" noone@somewhere wrote in message
...
I have a form which is used for data entry. It works fine for data
entry,
that is, the data is stored in the appropriate tables. However,

when
I
use
the same form to see data it will not allow me to see the newly

entered
data. Also the 'go to the end of records' button on the bottom of

the
form
will not allow me to look at data after record 1770 even though

there
are
more than 1786 records in the database. Filtering by form will

also
not
allow me to see anything over record 1770. The data is in the

tables.
I
can
open a table and see that the data is in fact present. Just the

form
won't
allow me to see new records above 1770.
This is Access 2002.

Any ideas why the form is not seeing new records? It can see all

the
older
records.

Help please?












  #7  
Old August 14th, 2004, 02:43 PM
rleblanc
external usenet poster
 
Posts: n/a
Default

As it turns out there are three major tables other than the client table:
finances, meals, and dependents. It is possible that some of these were
created without a record being related back to the masterID in the client
table. That would leave open the possibility of creating a record set
without one or more associated records in the three tables in question. To
"fix" this problem I am proposing to enter some default values such that
records are created in each of the tables regardless of whether there is
actual data to be put in. For instance, creating a "none" name for a child
in the dependents table will force the creation of an associated record and
allow the filter to find at least one appropriate record. The users of the
database will understand that a "none" last name is not a real person but
just a database artifact. Does that sound like a solution?

By the way, thanks for all your help. I'd have pulled my hair out figuring
this problem out! Thanks.

"'69 Camaro" wrote in message
...
Your query here is matching records in the "client" table with the records
in "misc" and "finances." There are 16 records in the "client" table that
have values in the MasterID field that have no matched records in one --

or
both -- of the other two tables. That's why these 16 records aren't

showing
up in the Recordset that is being used as the source of your Form.

You need to determine whether these 16 records should or shouldn't be
included in the Form's Recordset, but first you need to see *which*

records
are in the "client" table, but not in the other two tables.

To do so, create a new query. Paste this entire SQL statement into the

SQL
View pane:

SELECT Client.MasterID, Misc.MasterID, Finances.MasterID
FROM (Client LEFT JOIN Misc ON Client.MasterID = Misc.MasterID) LEFT JOIN
Finances ON Client.MasterID = Finances.MasterID
WHERE (IsNull(Misc.MasterID) OR IsNull(Finances.MasterID));

Run the query. In the Client.MasterID field you'll see which 16 unmatched
records aren't showing up on your Form when you open it. Wherever you see

a
blank in the field named Misc.MasterID or Finances.MasterID is where

there's
a record that *might* be missing from one of these other tables. I write
"might" because there may be a good reason that these records don't exist

in
these tables, but only you can decide that after you've gathered a little
more information.

Open the "client" table and search for the values in each of the 16

records
in the Client.MasterID field of the query you just created. Look at these
records and investigate why you may or may not need matching records in

the
"misc" or "finances" tables.

If there *should be* matching records in each of these 16 cases, then you
need to figure out why they aren't there. Perhaps someone forgot to add
these records in other data entry Forms. Perhaps these tables are results
of imports from a spreadsheet or another database that never needed any of
these 16 records. Or maybe there are other reasons.

So, you need to do some further investigation, but at least you know *why*
those records aren't showing up in your Form, and you know exactly which

16
records are in your "client" table, but aren't in either of the "misc" or
"finances" tables.

Good luck and post back if you have any further problems.

HTH.

Gunny

See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips.


"rleblanc" noone@somewhere wrote in message
...
The complete SQL statement is as follows:

SELECT client.MasterID, client.CreationDate, client.l_name,

client.f_name,
client.MI, client.SSN, client.DOB, client.Street, client.City,

client.State,
client.ZipCode, client.PhoneNumber, client.MaritalStatus,

client.AdultDeps,
client.Children, client.Seniors, finances.ClientWages,
finances.UnemployComp, finances.WorkersComp, finances.TANF,
finances.SSDisability, finances.SSI, finances.VeteranPension,
finances.SSRetirement, finances.ChildSupport, finances.SSSurvivor,
finances.RentalIncome, finances.FoodStamps, finances.OtherIncome,
finances.WIC, finances.RentAssistance, finances.FuelAssistance,
finances.CityWelfare, finances.TEFAPLetter, finances.IncomeMemo,
misc.[General Memo] FROM (client INNER JOIN misc ON
client.MasterID=misc.MasterID) INNER JOIN finances ON
client.MasterID=finances.MasterID;


"'69 Camaro" wrote in message
...
Excellent. Open the Form in "Design View." Open the Properties

window,
and
select the "Data" tab. Place your cursor in the "Record Source" text

area,
right in the part that reads "SELECT" and then press SHIFTF2 to

open
the
Zoom window. Copy and paste the entire SQL statement displayed in the

Zoom
window into your next post so that we may see it and analyze it to

determine
what's limiting your records.

By the way, when you make the "client" table the record source for

your
Form, you're getting the "#Name?" showing in the text boxes on the

form
that
are bound to the fields in the one or more other tables in the query.

Since
these fields don't exist in the "client" table, Access can't figure

out
what
field you want to bind each of these text boxes to.

HTH.

Gunny

See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips.


"rleblanc" noone@somewhere wrote in message
...
Data Entry is set to no.

Record Source is set to SELECT. There are no VBA modules in this

database
as
yet.

If I set the Record Source to "client" (which is the master table to

which
everything else is related), some of the fields get filled with

#name?
instead of the actual data. However, the data in the client table is
completely accessible.

Any more ideas?

"'69 Camaro" wrote in message
...
Check the Form's Record Source Property (on the Form Properties

"Data"
tab)
to see whether it is based upon a saved query whose criteria

excludes
your
newest records or whether there's a SQL statement that also

excludes
your
newest records.

If the Record Source Property isn't the culprit, look at the VBA

code
to
find a "Filter = ..." for this Form (the code doesn't actually

have
to
be
in
the Form's module, since your Form can be referenced elsewhere)
somewhere
that has criteria that excludes your newest records, as well as a
"FilterOn
= True" statement.

HTH.

Gunny

See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips.


"rleblanc" noone@somewhere wrote in message
...
I have a form which is used for data entry. It works fine for

data
entry,
that is, the data is stored in the appropriate tables. However,

when
I
use
the same form to see data it will not allow me to see the newly
entered
data. Also the 'go to the end of records' button on the bottom

of
the
form
will not allow me to look at data after record 1770 even

though
there
are
more than 1786 records in the database. Filtering by form will

also
not
allow me to see anything over record 1770. The data is in the

tables.
I
can
open a table and see that the data is in fact present. Just the

form
won't
allow me to see new records above 1770.
This is Access 2002.

Any ideas why the form is not seeing new records? It can see all

the
older
records.

Help please?














 




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

Similar Threads
Thread Thread Starter Forum Replies Last Post
selecting multiple records sps Using Forms 3 August 3rd, 2004 08:22 PM
append Query duplicating records Alex Running & Setting Up Queries 1 July 8th, 2004 01:31 PM
Query combining multiple records from one table can't add records Clint Marshall Running & Setting Up Queries 4 July 8th, 2004 01:25 PM
Copying new records John General Discussion 0 June 25th, 2004 04:02 PM
How to Manipulate the group and sorting in a report? Jorge Novoa Using Forms 2 June 9th, 2004 01:12 AM


All times are GMT +1. The time now is 04:17 AM.


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