Property value is too large

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance



I'm starting a database for opacity testing. I'm supposed to add fields for
every six minutes in a day that are numbers from 0 to 100, with the date
itself as the primary key. As you can tell, as there are ten 6 minute
intervals in an hour and 24 hours, I should only have 241 fields, but when I
add fields and save it, I get "Property value is too large", and I had all
the number fields in the table set to byte, since I'm not gonna have any
numbers over 127 or 128. I tried denormalization, and split the big table
into two tables, and used a one to one relationship with the two tables, by
adding a Date field to the second table too. I then placed them together in a
query, and then used that query as a record source for the data entry form,
but I get the same day there twice when I cycle through records, I only need
it there once. Can you help me there? If not as a posting, you can send it to
my address at clint_gould@xxxxxxxxxxx if you wish. If you need me to explain
the problem further, let me know.

Clint
.



Relevant Pages

  • Re: Form
    ... Some instruction of the fundamentals of database design may be in order. ... which is to say a table or query should be selected as its Record ... If you want to store data in the table by way of a form (which should always ... query as the form's Record Source, and select a field from the Record Source ...
    (microsoft.public.access.forms)
  • Re: Problem with Select INTO
    ... DoCmd.RunSQL = <3078-The Microsoft Jet database engine could not find ... the input table or query 'tbldata'. ... in the local MDB. ... case the table result) as the form's record source. ...
    (microsoft.public.access.formscoding)
  • Re: Problem with Select INTO
    ... DoCmd.RunSQL = <3078-The Microsoft Jet database engine could not find ... the input table or query 'tbldata'. ... in the local MDB. ... case the table result) as the form's record source. ...
    (microsoft.public.access.formscoding)
  • Re: Slow Database after splitting
    ... If it is on the network, this can have a negative impact on performance. ... Yes the Form 2 Query is not a proper name, was just used for saving the ... query built in the record source, then removing the record source, and ... By splitting I mean the database is still in Access .mdb. ...
    (microsoft.public.access.tablesdbdesign)
  • Re: Problem with Select INTO
    ... DoCmd.RunSQL = <3078-The Microsoft Jet database engine could not find ... the input table or query 'tbldata'. ... in the local MDB. ... case the table result) as the form's record source. ...
    (microsoft.public.access.formscoding)