Re: "Numeric field overflow."

An overflow indicates that a numeric value is outside the range of the field
Access is trying to append it to.

If the source query has calculated fields, you may need to typecast the
calculation with CDbl(), CCur(), CLng(), etc. You will probably need to use
Nz() inside that also, to avoid problems with Null.

Another possibility is that the field size in the target table is not
adequate. For example, a Number field of size Integer will not accept values
larger than 32767.

If the field sizes are not an issue, and typecasting does not solve the
problem, it is possible that Access is confused about what the query is
referrring to. Try unchecking the Name AutoCorrect boxes under:
Tools | Options | General
Then compact the database:
Tools | Database Utilities | Compact
Info on why:
http://allenbrowne.com/bug-03.html

A2003 is not less stable than previous versions. The query engine (JET 4) is
actually the same for Access 2000, 2002, and 2003. This engine is somewhat
less efficient (for example with user-defined function calls) and less
capable of recognising data types (on calculated fields) than its
predecessor (JET 3.5 in Access 97), but it is not less stable.

It is possible to configure A2003 so it is arguably the most stable version
of Access, at least since version 2. For info on how to do that, see:
Preventing corruption
at:
http://allenbrowne.com/ser-25.html

--
Allen Browne - Microsoft MVP. Perth, Western Australia.
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"G Lykos" <GLykos@xxxxxxxxxxxxxx> wrote in message
news:eUe%23bBkeGHA.1276@xxxxxxxxxxxxxxxxxxxxxxx
Am regularly running into a problem where something snaps and an append
query stops running with the captioned error message. I'm not doing any
math calculations, just appending selected fields from a filtered record
set.

Once this happens, it stays broken until I edit the query (as in add a
field, then delete it, functionally taking me back to when I started) and
then the query works again for a while. It's driving me nuts because I
don't know how to identify the source, and I'm tired of having to futs
around with nonsense edits to the query to get it working again. Any
ideas
what might be causing this??

I have the impression after having struggled with this and other oddball
Access things this week that Access 2003 SP2, under XP Pro with all
updates,
is kind of buggy. Were earlier releases more stable?

Thanks,
George


.

Relevant Pages

  • Re: Does DateDiff Have A Bug
    ... Now I just use the results from the query and everything works better than ... MemberID FirstName LastName EntryDate DaysRemaining ... calculated field within it's calculation) would look like; ... if there are zero days left which in ...
    (microsoft.public.access.formscoding)
  • Re: Does DateDiff Have A Bug
    ... I changed the form (Members) RecordSource back to my Main ... Now I just use the results from the query and everything works better than ... MemberID FirstName LastName EntryDate DaysRemaining ... calculated field within it's calculation) would look like; ...
    (microsoft.public.access.formscoding)
  • Re: Does DateDiff Have A Bug
    ... Now you would go to Queries/Create query in Design View, ... MemberID FirstName LastName EntryDate DaysRemaining ... calculated field within it's calculation) would look like; ... I'm trying to write the result of lngDays when it reaches zero days ...
    (microsoft.public.access.formscoding)
  • Re: Does DateDiff Have A Bug
    ... Now you would go to Queries/Create query in Design View, ... MemberID FirstName LastName EntryDate DaysRemaining ... calculated field within it's calculation) would look like; ... I'm trying to write the result of lngDays when it reaches zero days ...
    (microsoft.public.access.formscoding)
  • Re: Updating all records
    ... I'm assuming you can write a query that has a unique row for each PartID, ... and which contains one column for each "variable" used in the calculation, ... Dim sExpression as string ...
    (microsoft.public.access.formscoding)
Loading