By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
425,526 Members | 2,207 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 425,526 IT Pros & Developers. It's quick & easy.

Embarrassed to put this on the forum - but here goes anyway - can't see controls on form

P: n/a
MLH
I have a form, one of about 20 editing forms I created last
week. All were created pretty much the same way, used
the column wizard just to throw everything from the source
table/query up there. Then I modified from there, adding
buttons 'n whatnot.

I cannot see any controls on one of the 20 forms in form
view. They're all there in design. None have visible property
set to False. The controls are just not showing up. No matter
how many times I open it. I don't know what to do short of
rebuilding the form from scratch.

That's not the issue and I could do it in a short while. But
I really would like to know what's causing this. I don't like
being caught completely off-guard and don't want it to
happen again.
Nov 13 '05 #1
Share this Question
Share on Google+
10 Replies


P: n/a
MLH
I did check to see if the controls became visible if
the form's RecordSource property was removed
completely. And they did. When I put it back in,
they disappeared again. This should provide some
clue, but I can't figure it out.
Nov 13 '05 #2

P: n/a
Br
MLH <CR**@NorthState.net> wrote:
I have a form, one of about 20 editing forms I created last
week. All were created pretty much the same way, used
the column wizard just to throw everything from the source
table/query up there. Then I modified from there, adding
buttons 'n whatnot.

I cannot see any controls on one of the 20 forms in form
view. They're all there in design. None have visible property
set to False. The controls are just not showing up. No matter
how many times I open it. I don't know what to do short of
rebuilding the form from scratch.

That's not the issue and I could do it in a short while. But
I really would like to know what's causing this. I don't like
being caught completely off-guard and don't want it to
happen again.


Have you got any data in the data source? ie. if there is no data in the
table behind the form then you might not see any bound controls
(depending on how you set your forms up). Is the form setup to allow
additions/edits?
--
regards,

Bradley

A Christian Response
http://www.pastornet.net.au/response
Nov 13 '05 #3

P: n/a
Or the form's DataEntry property is set to Yes, and the form's recordsource
query is not updatable.

--

Ken Snell
<MS ACCESS MVP>

"Br@dley" <n0****@4u.com> wrote in message
news:jf*****************@news-server.bigpond.net.au...
MLH <CR**@NorthState.net> wrote:
I have a form, one of about 20 editing forms I created last
week. All were created pretty much the same way, used
the column wizard just to throw everything from the source
table/query up there. Then I modified from there, adding
buttons 'n whatnot.

I cannot see any controls on one of the 20 forms in form
view. They're all there in design. None have visible property
set to False. The controls are just not showing up. No matter
how many times I open it. I don't know what to do short of
rebuilding the form from scratch.

That's not the issue and I could do it in a short while. But
I really would like to know what's causing this. I don't like
being caught completely off-guard and don't want it to
happen again.


Have you got any data in the data source? ie. if there is no data in the
table behind the form then you might not see any bound controls (depending
on how you set your forms up). Is the form setup to allow additions/edits?
--
regards,

Bradley

A Christian Response
http://www.pastornet.net.au/response

Nov 13 '05 #4

P: n/a
MLH
Allow Edits, yes.
Allow Deletions, yes
Allow Additions, no

And, no, there is no data in the datasource (query). I have similar
editing forms bound to tables having no records. These do not
exhibit similar symptoms. I did test and the controls are all visible
if the source query returns data. It will, therefore, not present a
lasting problem since my data is permanent. But the behaviour
deserves some explanation since other forms based on record
sources returning no records display their empty source fields,
command buttons and other controls anyway. I thought it odd.

Have you got any data in the data source? ie. if there is no data in the
table behind the form then you might not see any bound controls
(depending on how you set your forms up). Is the form setup to allow
additions/edits?


Nov 13 '05 #5

P: n/a
MLH wrote:
Allow Edits, yes.
Allow Deletions, yes
Allow Additions, no

And, no, there is no data in the datasource (query). I have similar
editing forms bound to tables having no records. These do not
exhibit similar symptoms. I did test and the controls are all visible
if the source query returns data. It will, therefore, not present a
lasting problem since my data is permanent. But the behaviour
deserves some explanation since other forms based on record
sources returning no records display their empty source fields,
command buttons and other controls anyway. I thought it odd.


Is the underlying query editable? The "usual" blank form you are used to seeing
is actually the new record position. That is not available if the query does
not allow new records to be inserted.

--
I don't check the Email account attached
to this message. Send instead to...
RBrandt at Hunter dot com
Nov 13 '05 #6

P: n/a
MLH
The form's DataEntry property setting is No.
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Or the form's DataEntry property is set to Yes, and the form's recordsource
query is not updatable.


Nov 13 '05 #7

P: n/a
MLH
I checked the query, opening it in datasheet view. I manually added a
couple of records to it to make sure it was editable. The impact this
issue has on my app is negligible, as I have employed a workaround
to count the records returned by the query. I simply do not open the
form unless records are returned now. But you know how these things
are - sometimes you just wanna get to the bottom of it.

Thx for your contribution.

Is the underlying query editable? The "usual" blank form you are used to seeing
is actually the new record position. That is not available if the query does
not allow new records to be inserted.


Nov 13 '05 #8

P: n/a
Br
MLH <CR**@NorthState.net> wrote:
Allow Edits, yes.
Allow Deletions, yes
Allow Additions, no

And, no, there is no data in the datasource (query). I have similar
editing forms bound to tables having no records. These do not
exhibit similar symptoms. I did test and the controls are all visible
if the source query returns data. It will, therefore, not present a
lasting problem since my data is permanent. But the behaviour
deserves some explanation since other forms based on record
sources returning no records display their empty source fields,
command buttons and other controls anyway. I thought it odd.

Have you got any data in the data source? ie. if there is no data in
the table behind the form then you might not see any bound controls
(depending on how you set your forms up). Is the form setup to allow
additions/edits?


Ok, you either need data or to allow additions.....
--
regards,

Bradley

A Christian Response
http://www.pastornet.net.au/response
Nov 13 '05 #9

P: n/a
MLH <CR**@NorthState.net> wrote in
news:qr********************************@4ax.com:
The form's DataEntry property setting is No.


That combined with what you said in another post:

Allow Edits, yes.
Allow Deletions, yes
Allow Additions, no

Shows why it's blank if there are no records in the returned
recordsource. To not be blank, the form would have to move to a new
record, but your settings prohibit that.

--
David W. Fenton http://www.bway.net/~dfenton
dfenton at bway dot net http://www.bway.net/~dfassoc
Nov 13 '05 #10

P: n/a
BTW, I tend to open forms with a non-editable blank record and than
load the records the user requests. I also tend *not* to allow
addition of records in the same form as the data is edited, but
create it from an unbound form, then load the record into the form,
replacing the blank, non-editable recordsource with a recordsource
that returns the just-added record.

My reason for this is that I've seen too many users start typing
into the first record of a form. Thus, I make sure that there are no
editable records loaded, and that they have to do something else to
load a record for editing.

--
David W. Fenton http://www.bway.net/~dfenton
dfenton at bway dot net http://www.bway.net/~dfassoc
Nov 13 '05 #11

This discussion thread is closed

Replies have been disabled for this discussion.