Tags: access, created, database, error, maketable, message, microsoft, mysql, oracle, overflow, query, relatively, scientific, sql, working

Problem with Overflow error message in Access

On Database » Microsoft Access

4,021 words with 4 Comments; publish: Fri, 04 Jan 2008 11:33:00 GMT; (250140.63, « »)

Hi,

I'm new at using Microsoft Access (2000), and I've been working on a relatively simple scientific database. I've created a "MakeTable" query, which has worked well in the past and I update the table regularly as I enter more data. All the query does is run some calculations from data entered previously, and it puts the results of those calculations in this new table.

The last time I tried to update this table by running the query, I get the error message "Overflow". I'm not sure where to even start to fix the problem. I've searched the forum for answers, but it seems like all the overflows have to do with transfering data to SQL.

I would greatly appreciate some pointers on how to address this problem.

Thank you for your time.

Wiline

All Comments

Leave a comment...

  • 4 Comments
    • Quote:
      === Original Words ===

      Hi,

      I'm new at using Microsoft Access (2000), and I've been working on a relatively simple scientific database. I've created a "MakeTable" query, which has worked well in the past and I update the table regularly as I enter more data. All the query does is run some calculations from data entered previously, and it puts the results of those calculations in this new table.

      The last time I tried to update this table by running the query, I get the error message "Overflow". I'm not sure where to even start to fix the problem. I've searched the forum for answers, but it seems like all the overflows have to do with transfering data to SQL.

      I would greatly appreciate some pointers on how to address this problem.

      Thank you for your time.

      Wiline

      Well, the thing is that your make table query runs on SQL. So I suggest looking over those thread again. All queries in Access run from SQL. It's just that the design view for queries is a graphical user interface for those who don't know how to type SQL code.

      #1; Fri, 04 Jan 2008 11:34:00 GMT
    • Quote:
      === Original Words ===

      Hi,

      I'm new at using Microsoft Access (2000), and I've been working on a relatively simple scientific database. I've created a "MakeTable" query, which has worked well in the past and I update the table regularly as I enter more data. All the query does is run some calculations from data entered previously, and it puts the results of those calculations in this new table.

      The last time I tried to update this table by running the query, I get the error message "Overflow". I'm not sure where to even start to fix the problem. I've searched the forum for answers, but it seems like all the overflows have to do with transfering data to SQL.

      I would greatly appreciate some pointers on how to address this problem.

      Thank you for your time.

      Wiline

      The result of a calculation in the Query may be too large for the Field in the Table to which it will be appended. e.g. A Query calculation results in a Long Integer ( 1 to 2,147,483,647?). If this result is to be added to a Field in the new Table that's set to Integer, an Overflow Error will occur. You may have to redesign the Data Types of some Fields in the new Table. Hope this helps.

      #2; Fri, 04 Jan 2008 11:35:00 GMT
    • Adezii's probably right here; Error 6 in Access is almost always the result of trying to shovel 10 pounds of potatoes into a 5 pound sack! GO back and take a look at the limits for each of the numerical datatypes.
      #3; Fri, 04 Jan 2008 11:36:00 GMT
    • To view your query as SQL just open the query in design view as normal and then change the view to SQL. We use SQL all the time as it's easier to post in the forum.

      When you have the SQL view open copy and paste it in a post here so we can see if there is any obvious problems with it.

      Mary

      #4; Fri, 04 Jan 2008 11:37:00 GMT