Hi There, making up my first database: i have a problem where i have designed a form and everything in it can be seen in design view but when i view it in form view i get a blank background - no boxes pics, subform... can anyone lead me in the right direction - it is a form containing a subform - items in the form come from 3 different tables (all linked)
form blank
- Thread starter carelfly
- Start date
DCrake
Remembered
- Local time
- Today, 18:52
- Joined
- Jun 8, 2005
- Messages
- 8,626
It will most likely be because it is a bound form and the underlying record source does not contain any records.
Design the form and go to recordsource property and open it up from within the form. Go to datasheet view. Do any records appear?
Design the form and go to recordsource property and open it up from within the form. Go to datasheet view. Do any records appear?
hi - the records are empty - there is no data in them - i have checked all the fields in the form are linked to a data source but the problem is that the design of the form has vanished when i view the form - not only the data in the fields
Just adding to this. Copy the record source of your main form, paste it into the SQL view of a query and run it. See if any records are display. The joins between those three tables may be limiting the number of records returned.
If that fails, unlink the subform(s) from the main form and see the result.
If that fails, unlink the subform(s) from the main form and see the result.
missinglinq
AWF VIP
- Local time
- Today, 13:52
- Joined
- Jun 20, 2003
- Messages
- 6,420
How can it show the data in Datasheet View if, as you stated in your second post
When the controls, even if empty, do not show up, the cause is, as DCrake stated, because "...it is a bound form and the underlying record source does not contain any records..." and, and this is an important and, the recordset is Read-Only. This third thing has to also be true for this to happen.
If by
you mean that you can actually see the textboxes, which are empty, this doesn't mean that the query can be updated. The real test is can you then add a record directly to the query? If not, the query is Read-Only.
Allen Browne has an excellent short article on why queries are Read-Only:
http://allenbrowne.com/ser-61.html
Aside from a Read-Only query and AllowAdditions being set to No, other reasons for a form being Read-Only include the Recordset Type being set to Snapshot or the user not having Write Permission for the folder where the data resides.
Linq ;0)>
- Local time
- Today, 18:52
- Joined
- Sep 12, 2006
- Messages
- 16,052
you will get this effect if there are no records AND the recordsdource is not updateable
try opening the query, and try to add an item - see if it lets you - if not its not updateable
(which is the same as missinglinq just said)
try opening the query, and try to add an item - see if it lets you - if not its not updateable
(which is the same as missinglinq just said)
I think i have steered down the wrong alley - i have redone my form but in case it happens again -
when i designed the form with all the text boxes, checkboxes, fill-in-the-blanks, i kept clicking form view to check the form looked the way it was supposed to... suddenly when i clicked on form view everything had vanished, no text boxes, nothing - a blank screen with no entry points at all. i went back to design view and everything was there, it just doesn't show up on the form view. the problem is not the table because the data is editable in the table datasheet and through the query as directed before
when i designed the form with all the text boxes, checkboxes, fill-in-the-blanks, i kept clicking form view to check the form looked the way it was supposed to... suddenly when i clicked on form view everything had vanished, no text boxes, nothing - a blank screen with no entry points at all. i went back to design view and everything was there, it just doesn't show up on the form view. the problem is not the table because the data is editable in the table datasheet and through the query as directed before
- Local time
- Today, 18:52
- Joined
- Sep 12, 2006
- Messages
- 16,052
I am sure this will turn out to be related to the data in the form being non-updateable.
What values do you have for "allow additions" and "allow edits"
What values do you have for "allow additions" and "allow edits"
I have come back to the same problem again - when i am creating a form that has more than two sources (tables or queries), as soon as i add the third source and try view the form it gives me a blank page - in form view i have a completely blank screen - no controls, no subforms, no textboxes - doi need to change something to allow a third source in my form?
Access version 2007 - and 2003 after conversion from 2007
it is a stripped down version:
tables: customers, equipment, sale
forms for entry: customers, equipment, sale
query to calculate cost in the sale form: sale inv
at the moment the query is in the record source and it is causing the problem - as soon as i remove it from the record source my form appears. as i said it is just in the record source - i haven't even added any fields from it to the form yet.
it is a stripped down version:
tables: customers, equipment, sale
forms for entry: customers, equipment, sale
query to calculate cost in the sale form: sale inv
at the moment the query is in the record source and it is causing the problem - as soon as i remove it from the record source my form appears. as i said it is just in the record source - i haven't even added any fields from it to the form yet.
Your relationships is in a cyclical form making it a complex relationship and hence, unupdateable as previously pointed out. You need to revise your table designs following database "normalization" rules. Lookup that term.
thanks vbaInet - being new to databases i didn't understand how access obtains its data from different tables and thought i had to have a direct relationship between all tables i wanted to get data from rather than working through the single relationships between the tables.
Thanks
No, not at all 
The relationships have to be logical and if they've been setup correctly, you can "easily" use queries to extract information from one or more tables.
Here are some good links:
http://www.deeptraining.com/litwin/dbdesign/FundamentalsOfRelationalDatabaseDesign.aspx
http://www.databasedev.co.uk/database_design_requirements.html
http://support.microsoft.com/kb/234208
Don't forget to check out the Theory and Practice of Database Design section and feel free to post questions related to this on there.
Good luck!
The relationships have to be logical and if they've been setup correctly, you can "easily" use queries to extract information from one or more tables.Here are some good links:
http://www.deeptraining.com/litwin/dbdesign/FundamentalsOfRelationalDatabaseDesign.aspx
http://www.databasedev.co.uk/database_design_requirements.html
http://support.microsoft.com/kb/234208
Don't forget to check out the Theory and Practice of Database Design section and feel free to post questions related to this on there.
Good luck!
