Bizzare Form Behavior

  • Thread starter Thread starter Eric Levy
  • Start date Start date
E

Eric Levy

I'm working in Access 2000, and am experiencing some truly
strange behavior with several forms I'm trying to design.

The forms are very simple, as are the underlying tables.
The tables themselves only contain one or two fields each.
No expressions, no functions, etc. in the forms' fields.
Just simple text data.

Here's the problem: When I have one of (or any of) the
forms open in design view and switch to live data view, it
displays the data the way it's supposed to. But, when I
open the form for live data view directly from the
database project window, the fields only display "#NAME?".
Also, record counts are way off the mark when this happens.

I've monkeyed with the form and control properties until
I'm blue in the face, to no avail. The tables involved are
not linked to any other tables in any way.

So, am I just missing something stupid and obvious, or is
there really something strange going on here? I've reached
the end of my rope and am going to keep squeezing my
little stress ball.

Any help would be greatly appreciated.

Thanks.

Eric
 
Eric Levy said:
I'm working in Access 2000, and am experiencing some truly
strange behavior with several forms I'm trying to design.

The forms are very simple, as are the underlying tables.
The tables themselves only contain one or two fields each.
No expressions, no functions, etc. in the forms' fields.
Just simple text data.

Here's the problem: When I have one of (or any of) the
forms open in design view and switch to live data view, it
displays the data the way it's supposed to. But, when I
open the form for live data view directly from the
database project window, the fields only display "#NAME?".
Also, record counts are way off the mark when this happens.

I've monkeyed with the form and control properties until
I'm blue in the face, to no avail. The tables involved are
not linked to any other tables in any way.

So, am I just missing something stupid and obvious, or is
there really something strange going on here? I've reached
the end of my rope and am going to keep squeezing my
little stress ball.
Click to expand...

It sounds pretty strange to me. Did you create these forms yourself?
Do they have any code behind them at all? If so, please post the entire
code module of one of the forms that exhibits this behavior. Does it
happen with any other database, or just this one? Do you have a form
open, hidden perhaps, that is doing something in its Timer event? Does
it make any difference if you Compact and Repair the database? If you
make a new blank database and import all the objects from this one, (a)
do they all import, and (b) does the new database exhibit the same
behavior?
 
-----Original Message-----


It sounds pretty strange to me. Did you create these forms yourself?
Do they have any code behind them at all? If so, please post the entire
code module of one of the forms that exhibits this behavior. Does it
happen with any other database, or just this one? Do you have a form
open, hidden perhaps, that is doing something in its Timer event? Does
it make any difference if you Compact and Repair the database? If you
make a new blank database and import all the objects from this one, (a)
do they all import, and (b) does the new database exhibit the same
behavior?

--
Dirk Goldgar, MS Access MVP
www.datagnostics.com

(please reply to the newsgroup)


.
Click to expand...

Dirk,

Thanks for your reply. I did manage to get it fixed. Seems
that it was just another goofy Windows/Office/_Microsoft_
anomoly.

The cure seems to have been temporarily changing the
form's border style, saving it, closing it, then re-
opening it and changing it back to what I originally
wanted. I went through this process on each form that was
giving me trouble and it seems to have worked. After that
I restarted the computer and curled up in a ball in the
corner and shivered for a while.

In response to your questions, this is a new database that
I am designing. So far there is no real code running,
other than one 30 second timer on each form to keep a
current time display. The only data is sample data in the
small lookup tables that were giving me the trouble.

Thanks again.

Eric
 
Eric Levy said:
Thanks for your reply. I did manage to get it fixed. Seems
that it was just another goofy Windows/Office/_Microsoft_
anomoly.

The cure seems to have been temporarily changing the
form's border style, saving it, closing it, then re-
opening it and changing it back to what I originally
wanted. I went through this process on each form that was
giving me trouble and it seems to have worked. After that
I restarted the computer and curled up in a ball in the
corner and shivered for a while.

In response to your questions, this is a new database that
I am designing. So far there is no real code running,
other than one 30 second timer on each form to keep a
current time display. The only data is sample data in the
small lookup tables that were giving me the trouble.
Click to expand...

That's certainly bizarre, and a new one on me. How did you come up with
your cure? Is this a known bug? Do you think the Timer event, or the
code in it, is implicated?
 
-----Original Message-----


That's certainly bizarre, and a new one on me. How did you come up with
your cure? Is this a known bug? Do you think the Timer event, or the
code in it, is implicated?

--
Dirk Goldgar, MS Access MVP
www.datagnostics.com

(please reply to the newsgroup)


.
Click to expand...

I had no real logical procedure to coming up with my fix.
I just kept trying out of sheer frustration. I figured
that eventually either myself or someone else would come
up with something. I had already tried just about
everything else.

I honestly don't know if it's a known bug or not. I've
never seen it before, but I don't do a whole lot in
Access, either. I couldn't find anything on Microsoft's
site that mentioned it. Then again, how exactly do you
build that search phrase for the engine? It would be
complicated (and painful)!

I don't think that the Timer event had anything to do with
it, as I am using that same code in other forms that have
not exhibited this problem.

Dunno. Just shrugging my shoulders and glad it's working.
 
Back
Top