Eric Butts said:Wow... that's a lot of information!!
I'll try my best to give you the best advice.
"...We are to collect info from them for three consecutive months. At
first, I decided that it would be easier if I had a table for each month
just to keep things simple when trying to create a query based on this
three months..."
- Normalize your data by creating ONE table that has a field for the month,
example
RecordID TransAmt CustomerID fldMONTH
This way you can create your query displaying your data for the particular
months of interest.
I hope this helps.
Regards,
Eric Butts
Microsoft Access Support
(e-mail address removed)
"Microsoft Security Announcement: Have you installed the patch for
Microsoft Security Bulletin MS03-026? If not Microsoft strongly advises
you to review the information at the following link regarding Microsoft
Security Bulletin MS03-026
<http://www.microsoft.com/security/security_bulletins/ms03-026.asp> and/or
to visit Windows Update at <http://windowsupdate.microsoft.com/> to install
the patch. Running the SCAN program from the Windows Update site will help
to insure you are current with all security patches, not just MS03-026."
This posting is provided "AS IS" with no warranties, and confers no rights
--------------------
| Thread-Topic: Error message -- "property value is too large"
| thread-index: AcR2WrRGoSsd3LDORJq2bqYhN/viyg==
| X-WBNR-Posting-Host: 168.215.135.201
| From: =?Utf-8?B?dGl6?= <[email protected]>
| References: <[email protected]>
<[email protected]>
| Subject: RE: Error message -- "property value is too large"
| Date: Fri, 30 Jul 2004 10:29:01 -0700
| Lines: 72
| Message-ID: <[email protected]>
| MIME-Version: 1.0
| Content-Type: text/plain;
| charset="Utf-8"
| Content-Transfer-Encoding: 8bit
| X-Newsreader: Microsoft CDO for Windows 2000
| Content-Class: urn:content-classes:message
| Importance: normal
| Priority: normal
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
| Newsgroups: microsoft.public.access.tablesdbdesign
| NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.1.29
| Path: cpmsftngxa10.phx.gbl!TK2MSFTNGXA03.phx.gbl
| Xref: cpmsftngxa10.phx.gbl microsoft.public.access.tablesdbdesign:82192
| X-Tomcat-NG: microsoft.public.access.tablesdbdesign
|
| Eric:
| I was assigned to create a db in access for different customers. We are
to collect info from them for three consecutive months. At first, I decided
that it would be easier if I had a table for each month just to keep things
simple when trying to create a query based on this three months. I also
have an additional table with the customer’s info and one field in this
table is called Business Days. The primary key of the customer’s info
table is called Customer’s Code, this is a value that I assign manually.
When trying to create a query based on these four tables, I encountered a
small problem when trying to divide by Business Days. To this, somebody
pointed out that even though each Customer’s Code had only one specified
number for Business Days, access didn’t quite understand this. He solved
my problem by putting a “MAX†in front of Business Days.
|
| The next problem was encountered when trying to create a form out of the
four tables and the query. I wanted to do this because the people that will
be using the database will like to see all of this information at once.
They actually have their info in Excel, but they are entering so much data
in that they are worried that it will get corrupted, and decided that it
was better to have the info in access. I tried to use the wizard at first,
but a message shows up and it is practically letting me know that I cannot
create a form based on those four tables and that query because the query
is based on those tables. Don’t quite understand the reason for this.
|
| So then, I decided to have just two tables, one for the customer’s info
and one for the three months. That is when the “property value messageâ€Â
started showing up. I read the advice you age this other girl and it really
helped me, so that is why I’m writing you. The new table I was trying to
create was going to have 196 fields with extra large names, but after the
problem I encountered, and after reading the info in your link, I decided
to follow resolution method # 2. Therefore, at this point I’m back to my
four tables. So now my problem is basically the form I have to create.
I’m starting to wonder if it would be better to keep this info in excel
basically because of presentation issues. Or would it be better to have a
combination of both? At this point, I believe that they would prefer
everything in access. So if you have access suggestions before offering a
combination of both, it would be awesome. I also believe that it is
important to know that I’m not an access master.
|
| Thanks very much for your time and sorry for such a long reply.
|
| B
|
| "Eric Butts [MSFT]" wrote:
|
| > Hi,
| >
| > Sounds as if you are running into the issue noted in the following:
| >
| > ACC2000: Error Saving Table Error Message After Design Change (323657)
| > http://support.microsoft.com/default.aspx?scid=KB;EN-US;323657
| >
| >
| > I hope this helps! If you have additional questions on this topic,
please
| > respond back to this posting.
| >
| >
| > Regards,
| >
| > Eric Butts
| > Microsoft Access Support
| > (e-mail address removed)
| > "Microsoft Security Announcement: Have you installed the patch for
| > Microsoft Security Bulletin MS03-026? If not Microsoft strongly
advises
| > you to review the information at the following link regarding Microsoft
| > Security Bulletin MS03-026
| > <http://www.microsoft.com/security/security_bulletins/ms03-026.asp>
and/or
| > to visit Windows Update at <http://windowsupdate.microsoft.com/> to
install
| > the patch. Running the SCAN program from the Windows Update site will
help
| > to insure you are current with all security patches, not just MS03-026."
| >
| > This posting is provided "AS IS" with no warranties, and confers no
rights
| >
| >
| > --------------------
| > | Thread-Topic: Error message -- "property value is too large"
| > | thread-index: AcRwwqhVwWCSnG91SJ6rnwft9vv+DA==
| > | X-WBNR-Posting-Host: 198.182.163.102
| > | From: =?Utf-8?B?bGl6YmdyZWVu?= <[email protected]>
| > | Subject: Error message -- "property value is too large"
| > | Date: Fri, 23 Jul 2004 07:38:02 -0700
| > | Lines: 1
| > | Message-ID: <[email protected]>
| > | MIME-Version: 1.0
| > | Content-Type: text/plain;
| > | charset="Utf-8"
| > | Content-Transfer-Encoding: 7bit
| > | X-Newsreader: Microsoft CDO for Windows 2000
| > | Content-Class: urn:content-classes:message
| > | Importance: normal
| > | Priority: normal
| > | X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
| > | Newsgroups: microsoft.public.access.tablesdbdesign
| > | NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.157
| > | Path: cpmsftngxa06.phx.gbl!TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA03.phx.gbl
| > | Xref: cpmsftngxa06.phx.gbl
microsoft.public.access.tablesdbdesign:82107
| > | X-Tomcat-NG: microsoft.public.access.tablesdbdesign
| > |
| > | I'm putting a survey into Access and after my last round of updates
to a
| > table, when I try to save it I get an error message saying "property
value
| > is too large". Does anyone know what this means, or how to get rid of
it?
| > |
| >
| >
|
Want to reply to this thread or ask your own question?
You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.