Cannot view form in form view

[JenS]

This seems relatively simple but I can't fix it. I have been creating forms
using the wizard with no problems for several months. However, all of a
sudden, when I use the wizard to create a form, I cannot view anything
(except the header) in form view. In design view everything sems to be in
working order, but when I swith to form view the page is blank, and I can't
enter any data. Does anyone have any suggestions they can offer? I have
beem messing with this for hours and can't figure it out.

Thanks for any help or suggestions!

Jen S.

 

[Gina Whipp]

JenS,

Is the form is based on a query? If yes, then it might be there's no data
in the query. Check the query to see what results you get.

 

[JenS]

Hi Gina,

thanks for responding! It's not based on a query, it is a form made using
fields from several tables for the purpose of simply entering data ( which
for obvious reasons I am unable to do!) This has always worked for me in the
past and I'm not doing anything different - its very puzzling.

JenS,

Is the form is based on a query? If yes, then it might be there's no data
in the query. Check the query to see what results you get.

This seems relatively simple but I can't fix it. I have been creating
forms

[quoted text clipped - 9 lines]

Jen S.

 

[Gina Whipp]

Jen,

If you from is based on fields from several tables in essence it is based on
a query. The only way you base any one form on several tables is if you use
some sort of SQL. And that suggest that the SQL is not working. Please
post the SQL and how those tables are joined.

--
Gina Whipp

"I feel I have been denied critical, need to know, information!" - Tremors
II

Hi Gina,

thanks for responding! It's not based on a query, it is a form made using
fields from several tables for the purpose of simply entering data ( which
for obvious reasons I am unable to do!) This has always worked for me in
the
past and I'm not doing anything different - its very puzzling.

JenS,

Is the form is based on a query? If yes, then it might be there's no data
in the query. Check the query to see what results you get.

This seems relatively simple but I can't fix it. I have been creating
forms

[quoted text clipped - 9 lines]

Jen S.

 

[JenS via AccessMonster.com]

Hi Gina,

I guess I don't know nearly as much as I thought I did - after getting your
message I had to go on line and read all about SQL's! I am not sure how to
post the SQL since I couldn't even manage to find it anywhere. Could you
help? I feel absolutely clueless now.

Jen

 

[Gina Whipp]

Jen,

No worries...

1. Open the form in design view
2. If the properties window is not open, go the menu above find the
properties button and press it once a window should open
3. The first line in the properties window says Record Source, click on
that line and then click the button with the 3 dots on it and another window
should open up
4. Under "File" in the upper left hand corner you will see a grid with an
arrow next to it, click the arrow and select 'SQL', your view will change.
5. Copy everything in that window and paste it to your message
6. When closing do NOT save any changes...

 

[JenS via AccessMonster.com]

Hmmm... therein lies the problem - there is no line that says record source.
When I look at my other forms that are based on a single table and I do what
you outline here, you are absolutely right in that the first line says Record
Source, but in this form, that's not the case - this one starts with Name,
then Force New Page, then New Row or Column and so on. Does that quirk alone
provide any insight?

I really appreciate your help with this! I will be away from the computer
for a few hours but will check in with you as soon as I get back to the
office. Thank you so much!

Jen

Jen,

No worries...

1. Open the form in design view
2. If the properties window is not open, go the menu above find the
properties button and press it once a window should open
3. The first line in the properties window says Record Source, click on
that line and then click the button with the 3 dots on it and another window
should open up
4. Under "File" in the upper left hand corner you will see a grid with an
arrow next to it, click the arrow and select 'SQL', your view will change.
5. Copy everything in that window and paste it to your message
6. When closing do NOT save any changes...

Hi Gina,

[quoted text clipped - 6 lines]

Jen

 

[Gina Whipp]

Jen,

Okay, that is because you are looking at the Properties for the sections and
not the form. So go thru the steps I provied with one exception.

AFTER Step 2, in the upper left hand corner is a small box where the rulers
meet. Click there once and a little box box should appear and the
Properties window should now Record Source. Then you can go on to the
balance of the steps.
--
Gina Whipp

"I feel I have been denied critical, need to know, information!" - Tremors
II

Hmmm... therein lies the problem - there is no line that says record
source.
When I look at my other forms that are based on a single table and I do
what
you outline here, you are absolutely right in that the first line says
Record
Source, but in this form, that's not the case - this one starts with Name,
then Force New Page, then New Row or Column and so on. Does that quirk
alone
provide any insight?

I really appreciate your help with this! I will be away from the computer
for a few hours but will check in with you as soon as I get back to the
office. Thank you so much!

Jen

Jen,

No worries...

1. Open the form in design view
2. If the properties window is not open, go the menu above find the
properties button and press it once a window should open
3. The first line in the properties window says Record Source, click on
that line and then click the button with the 3 dots on it and another
window
should open up
4. Under "File" in the upper left hand corner you will see a grid with an
arrow next to it, click the arrow and select 'SQL', your view will change.
5. Copy everything in that window and paste it to your message
6. When closing do NOT save any changes...

Hi Gina,

[quoted text clipped - 6 lines]

Jen

 

[JenS via AccessMonster.com]

Thanks Gina and I'm sorry for my delay in replying... I did as you suggested
and this is what I ended up with:

SELECT tblCollectionData.SpeciesCode, tblCollectionData.[Survey Day],
tblCollectionData.[Survey Month], tblCollectionData.[Survey Year],
tblCollectionData.Site, tblCollectionData.Subsite, tblCollectionData.[Total
Count], tblCollectionData.Males, tblCollectionData.Females, tblCollectionData.
[Collection Method], tblCollectionData.[Life Stage], tblCollectionData.[Host
Plant], tblCollectionData.Source, tblCollectionData.Collector,
tblCollectionData.[Determined By], tblCollectionData.[Known Exotic?],
tblCollectionData.Notes, tblSiteInformation.County, tblSiteInformation.Quad,
tblSiteInformation.PhysProv, tblSiteInformation.Habitat, tblSiteInformation.
Latitude, tblSiteInformation.Longitude, tblSiteInformation.Directions
FROM tblSiteInformation INNER JOIN tblCollectionData ON tblSiteInformation.
Site = tblCollectionData.Site;

Does this help?

Jen

 

[Gina Whipp]

In both tables there is a field called Site. Do they both contain data? Or
does one contain data and the other not? And are these two tables related
in any way PrimaryKey/ForeignKey, etc...

 

[Gina Whipp]

SELECT tblCollectionData.SpeciesCode, tblCollectionData.[Survey Day],
tblCollectionData.[Survey Month], tblCollectionData.[Survey Year],
tblCollectionData.Site, tblCollectionData.Subsite, tblCollectionData.[Total
Count], tblCollectionData.Males, tblCollectionData.Females,
tblCollectionData.
[Collection Method], tblCollectionData.[Life Stage], tblCollectionData.[Host
Plant], tblCollectionData.Source, tblCollectionData.Collector,
tblCollectionData.[Determined By], tblCollectionData.[Known Exotic?],
tblCollectionData.Notes, tblSiteInformation.County, tblSiteInformation.Quad,
tblSiteInformation.PhysProv, tblSiteInformation.Habitat, tblSiteInformation.
Latitude, tblSiteInformation.Longitude, tblSiteInformation.Directions
FROM tblSiteInformation INNER JOIN tblCollectionData ON tblSiteInformation.
Site = tblCollectionData.Site;


Change INNER to LEFT if you want to see everything from tblCollectionData
Change INNER to RIGHT if you want to see everything from tblSiteInformation

 

[JenS via AccessMonster.com]

Actually, since this is a new database, there hasn't been any data entered
yet in either of those tables. It is the same field - both tables have a
site and a subsite, but these will contain the same information. I was
advised it the SiteInformation table to do a double primary key for those two
fields, and they would be related to the site and subsite foreign keys in the
collection data table. Does that make sense the way I am explaining it?

Do I need to have some data entered before I start this form? I was thinking
that even though this form is more complex than others I have used that are
based on a single table, that I would just enter all the data for those two
tables using the form and that it would then just transfer that information
to those tables.

Jen

In both tables there is a field called Site. Do they both contain data? Or
does one contain data and the other not? And are these two tables related
in any way PrimaryKey/ForeignKey, etc...

Thanks Gina and I'm sorry for my delay in replying... I did as you
suggested

[quoted text clipped - 22 lines]

Jen

 

[Gina Whipp]

Jen<

tblSiteInformation a PrimaryKey, not sure why you were told to have a two
PK's but you need one the is indexed (No Duplicates), then tblCollectionData
needs the ForeignKey SiteID (no need to index). Then in the relationship
window drop the two tables in and create the link.

Why do you need to do this because I fear the way you have it set up you
will not be able to enter information in the form the way they are joined
together. Also note you shouldn't use this one form to enter information
for both tables. tblCollectionData will not let you enter any information
in the Site Field that is not already in the tblSiteInformation table.

--
Gina Whipp

"I feel I have been denied critical, need to know, information!" - Tremors
II

Actually, since this is a new database, there hasn't been any data entered
yet in either of those tables. It is the same field - both tables have a
site and a subsite, but these will contain the same information. I was
advised it the SiteInformation table to do a double primary key for those
two
fields, and they would be related to the site and subsite foreign keys in
the
collection data table. Does that make sense the way I am explaining it?

Do I need to have some data entered before I start this form? I was
thinking
that even though this form is more complex than others I have used that
are
based on a single table, that I would just enter all the data for those
two
tables using the form and that it would then just transfer that
information
to those tables.

Jen

In both tables there is a field called Site. Do they both contain data?
Or
does one contain data and the other not? And are these two tables related
in any way PrimaryKey/ForeignKey, etc...

Thanks Gina and I'm sorry for my delay in replying... I did as you
suggested

[quoted text clipped - 22 lines]

Jen

 

[JenS via AccessMonster.com]

I was trying to follow the rule of having several small tables but do you
think in this case I should combine the siteinformation and collection data
tables? I am using almost every field in both those tables on the form
anyway.
Jen

Jen<

tblSiteInformation a PrimaryKey, not sure why you were told to have a two
PK's but you need one the is indexed (No Duplicates), then tblCollectionData
needs the ForeignKey SiteID (no need to index). Then in the relationship
window drop the two tables in and create the link.

Why do you need to do this because I fear the way you have it set up you
will not be able to enter information in the form the way they are joined
together. Also note you shouldn't use this one form to enter information
for both tables. tblCollectionData will not let you enter any information
in the Site Field that is not already in the tblSiteInformation table.

Actually, since this is a new database, there hasn't been any data entered
yet in either of those tables. It is the same field - both tables have a

[quoted text clipped - 27 lines]

 

[Gina Whipp]

Jen,

Unless every piece of data has different Site Information then the answer is
no. You have set it up correctly. (Also note, it's not small tables it's
relational design.)

--
Gina Whipp

"I feel I have been denied critical, need to know, information!" - Tremors
II

I was trying to follow the rule of having several small tables but do you
think in this case I should combine the siteinformation and collection
data
tables? I am using almost every field in both those tables on the form
anyway.
Jen

Jen<

tblSiteInformation a PrimaryKey, not sure why you were told to have a two
PK's but you need one the is indexed (No Duplicates), then
tblCollectionData
needs the ForeignKey SiteID (no need to index). Then in the relationship
window drop the two tables in and create the link.

Why do you need to do this because I fear the way you have it set up you
will not be able to enter information in the form the way they are joined
together. Also note you shouldn't use this one form to enter information
for both tables. tblCollectionData will not let you enter any information
in the Site Field that is not already in the tblSiteInformation table.

Actually, since this is a new database, there hasn't been any data
entered
yet in either of those tables. It is the same field - both tables have
a

[quoted text clipped - 27 lines]

Jen

 

[JenS via AccessMonster.com]

Hi Gina,

I am going to have to send you flowers once we are done with this...

ok, so since every piece of data will not have different site information,
the person doing the data entry will esentially have to fill out 2 forms?
One for collection data and another for site information? And they would
have to fill out the site information form first because otherwise they can't
include the site in the collection data form?

That's ok it just seems like a pain to have to deal with 2 forms every time
they have a new specimen to deal with. Is this a case where I should use a
subform?

Jen,

Unless every piece of data has different Site Information then the answer is
no. You have set it up correctly. (Also note, it's not small tables it's
relational design.)

I was trying to follow the rule of having several small tables but do you
think in this case I should combine the siteinformation and collection

[quoted text clipped - 24 lines]

 

[Gina Whipp]

Jen,

Actually, once you enter the site information once then whenever the SiteID
is entered the information on the collection side should automatically show
up. (Provided the relationships are set up properly).

If it were me, I would have a seperate form to enter the Site Information.
Then when I enter the Collection Data and pick a SiteID all is done for me.
A button to open the form to enter the Site Information (which can be placed
on the form where the Collection Data is entered) should suffice.

--
Gina Whipp

"I feel I have been denied critical, need to know, information!" - Tremors
II

Hi Gina,

I am going to have to send you flowers once we are done with this...

ok, so since every piece of data will not have different site information,
the person doing the data entry will esentially have to fill out 2 forms?
One for collection data and another for site information? And they would
have to fill out the site information form first because otherwise they
can't
include the site in the collection data form?

That's ok it just seems like a pain to have to deal with 2 forms every
time
they have a new specimen to deal with. Is this a case where I should use
a
subform?

Jen,

Unless every piece of data has different Site Information then the answer
is
no. You have set it up correctly. (Also note, it's not small tables it's
relational design.)

I was trying to follow the rule of having several small tables but do you
think in this case I should combine the siteinformation and collection

[quoted text clipped - 24 lines]

Jen

 

[Gina Whipp]

Oh, no flowers neccessary... just glad to give back what has been given to
me!

--
Gina Whipp

"I feel I have been denied critical, need to know, information!" - Tremors
II

Hi Gina,

I am going to have to send you flowers once we are done with this...

ok, so since every piece of data will not have different site information,
the person doing the data entry will esentially have to fill out 2 forms?
One for collection data and another for site information? And they would
have to fill out the site information form first because otherwise they
can't
include the site in the collection data form?

That's ok it just seems like a pain to have to deal with 2 forms every
time
they have a new specimen to deal with. Is this a case where I should use
a
subform?

Jen,

Unless every piece of data has different Site Information then the answer
is
no. You have set it up correctly. (Also note, it's not small tables it's
relational design.)

I was trying to follow the rule of having several small tables but do you
think in this case I should combine the siteinformation and collection

[quoted text clipped - 24 lines]

Jen

 

[JenS via AccessMonster.com]

Hi Gina! I spent some time over the weekend messing around with this and I
think I got it. I liked your idea about entering the data on 2 seperate
tables/forms, but the problem was that I already had that going on - the data
entry person had to first enter all the species on a species table, then deal
with the form housing information on collection data and site information.
What I decided to do was create a subform for site information on the
collection data form. I entered some dummy data and it seems to be working!
Everything that gets entered shows up on both tables, and the drop down menus
get updated correctly, etc. I need to really mess with it more to work out
the kinks but I think the basic idea is sound. That also enabled me to get
rid of the double primary key jazz, which I admit I was uncomfortable about
even though the instructor for my access class assurred me that it would work.


Anyway, I will post a small note to you in a week or two after I've had a
chance to start entering some real data and really try it out, but wanted to
thank you so much for all of your help! This dialouge really helped point
out some basic things I needed to doi (and shouldn't do) and really helped me
understand the forms process a lot better. Thanks so much!

Jen

Oh, no flowers neccessary... just glad to give back what has been given to
me!

Hi Gina,

[quoted text clipped - 25 lines]

 

[Gina Whipp]

Your most welcome!

And THANK YOU for posting back!

--
Gina Whipp

"I feel I have been denied critical, need to know, information!" - Tremors
II

Hi Gina! I spent some time over the weekend messing around with this and
I
think I got it. I liked your idea about entering the data on 2 seperate
tables/forms, but the problem was that I already had that going on - the
data
entry person had to first enter all the species on a species table, then
deal
with the form housing information on collection data and site information.
What I decided to do was create a subform for site information on the
collection data form. I entered some dummy data and it seems to be
working!
Everything that gets entered shows up on both tables, and the drop down
menus
get updated correctly, etc. I need to really mess with it more to work
out
the kinks but I think the basic idea is sound. That also enabled me to
get
rid of the double primary key jazz, which I admit I was uncomfortable
about
even though the instructor for my access class assurred me that it would
work.


Anyway, I will post a small note to you in a week or two after I've had a
chance to start entering some real data and really try it out, but wanted
to
thank you so much for all of your help! This dialouge really helped point
out some basic things I needed to doi (and shouldn't do) and really helped
me
understand the forms process a lot better. Thanks so much!

Jen

Oh, no flowers neccessary... just glad to give back what has been given
to
me!

Hi Gina,

[quoted text clipped - 25 lines]

Jen