Orders Form Won't show all orders or entry of new???

[EZ KEY]

I opened my [Client Orders] form where I enter orders placed by Clients. Now
it only shows "1 of 1" and it won't let me enter any information. Any
thoughts. I don't recall any changes. My "Data Entry" says No, so it should
be showing all me to scan through all orders entered. Should be 10 in all.

Thanks!

 

[snaux]

I opened my [Client Orders] form where I enter orders placed by Clients. Now
it only shows "1 of 1" and it won't let me enter any information. Any
thoughts. I don't recall any changes. My "Data Entry" says No, so it should
be showing all me to scan through all orders entered. Should be 10 in all.

A few things (there are others, but these came to mind first, since
this happened to me last month).

1) Make sure it's a dynaset, and that it points to a table and not to a
query based on a table. Some query-based forms CAN be updated, but it's
all too easy to slip in a SQL call that screws the pooch.

2) Linked tables can't be updated: the table must be internal.

3) To make sure everything shows up, it helps to make a VBA call to
MoveLast, which forces everything to load.

4) Make sure the form is set to show "Continuous Forms"

5) It's best practice to do data entry on a single-item form, not on
continuous forms. Access is fickle about this, which is probably what
got you in trouble in the first place; even though YOU didn't change
anything, Access may have "helped" you by making the change for you,
just like it efficiently mangles working SQL queries into useless hash
when you close them.

Regarding item #5: Always keep in mind that in general, Microsoft
prefers self-taught hackers over educated computer scientists, because
hackers find a way to get the job done "good enough" in time for
impromptu stockholder presentations, which is better than doing things
*right* and on schedule. Bugs can always be spun as features.

I'm not making this up - I've actually heard MS Managers/Whores saying
this in front of large audiences, in one case to a bunch of computer
science PhDs. You could almost hear the tar bubbling in the back of the
room.

That the afore-mentioned hackers are in turn used to train the thousand
monkeys that actually bang out the final code is pure speculation, but
at least they keep the MVPs on their toes, and employed... hey, they DO
PAY the MVPs, right???

 

[John Vinson]

2) Linked tables can't be updated: the table must be internal.

WHAT!?

You're seriously mistaken here, Snaux. Or tens of thousands of
frontend/backend databases all over the world must be working by
magic...

3) To make sure everything shows up, it helps to make a VBA call to
MoveLast, which forces everything to load.

... keep the MVPs on their toes, and employed... hey, they DO
PAY the MVPs, right???

Nope. We're all volunteers, and being employed by MS disqualifies one
from being an MVP.

John W. Vinson[MVP]

 

[missinglinq via AccessMonster.com]

I'm also confused by this part of your reply:

4) Make sure the form is set to show "Continuous Forms"

5) It's best practice to do data entry on a single-item form, not on
continuous forms.

So which are you advising? Continuous form or non-continuous?

 

[Snaux]

WHAT!?

You're seriously mistaken here, Snaux. Or tens of thousands of
frontend/backend databases all over the world must be working by
magic...

My bad; I've been up all night helping my ex with her disertation.
QUALIFIER: tables linked to SOME external resources can't be updated,
at least easily. Obviously, linking to "real" external databases works
just fine. The problem arises with non-database data sources, such as
text files or spreadsheets. You can still do it with patience and VBA,
but read/write with pure Access to some data types is difficult, if not
impossible, unless there's some miracle command I've missed. Which
still doesn't make any since since Access can output to Excel format
anyways, but now we're back to that thousand-monkey theory again.

Regarding Continuous/NonContinuous forms: I think the MS Help pages
said something about using Continuous to list your results, then
clicking on a result would open up another non-continuous, but
editable, form to do your dirty work. Personally, I hate the extra
step, and want to simply edit my data en masse, but since following
their advice many little quirks have gone away.

I had a similar problem about a month ago; everything was working fine
until enough records got added that the scrollbars got triggered. At
that point, Access started "fixing things" for me, like not showing all
the records and treating dynasets like snapshots. My personal favorite
was when all the fields would allow you to edit them, but they'd revert
to original data when you left the field... and it would only happen
when scrollbars would have been made visble by the number of results
returned. Thousand Monkeys... go figure.

Which leads to another chunk of advice: COMPACT AND REPAIR *OFTEN*....
put it in your closedb routine if you must, or put it on a daily timer,
but do it... it fixes all sorts of weirdness.

 

[Gina Whipp]

Just curious, I know you said Data Entry is set to no but is the subform in
Continous View? Single View will only show one record.

--
Gina Whipp

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

 

[Gina Whipp]

I see Al is already answering this in another thread... so I'm moving
along.

Gina Whipp

I think I know what is causing the problem, but I don't know how to fix it.
When I did the following it causes this problem. When I clear it,
permanently damages the form unusable.

In the General Questions I asked how to setup a sales tax that would be
updated but not changed and this is how I was told to set it up. In the
footer is a [Sales Tax] field from the [Sales Tax] table that uses a
DLookup
to find the rate. In the Details there is a [Sales Tax] field that is
from
the [Orders] table that takes the rate in the footer multiplied by the
Subtotal in the [Order Details] subform to get the Sales Tax displayed in
the
Details of the form. The fields used are:

In the [Order Details] subform an unbound text box in the footer named:
[Subtot]

In the [Client Orders] form Details section, a bound text box from the
[Orders] table named: [Sales Tax]

In the [Client Orders] form Footer section, a bound text box from the
[Sales
Tax] table named: [Sales Tax_Sales Tax]

The [Sales Tax_Sales Tax] bound text box in the footer has a Default
Value:
=DLookUp("[Sales Tax]","[Sales Tax]")

The [Sales Tax] bound text box in the Details has a Control Source:
=[Order
Details].[Form]![SubTot]*[Forms]![Client Orders]![Sales Tax_Sales Tax]

WHAT!?

You're seriously mistaken here, Snaux. Or tens of thousands of
frontend/backend databases all over the world must be working by
magic...



Nope. We're all volunteers, and being employed by MS disqualifies one
from being an MVP.

John W. Vinson[MVP]