Getting a #size error
It works fine as long as none of the values are null. If one's null I get a #type error, so I changed the formula to
=Nz([Labor_WIP subform].[Form]![LaborWIPSubtotal],0) Nz([Vehicle_WIP subform].[Form]![KMWIPSubtotal],0) Nz([EquipmentWIP subform].[Form]![EquipmentWIPSubotal],0)
But now I'm getting a #size error instead. Again, it works fine, as long as there are no null's in there, but a null throws it off.
Or what even causes a #size error?
Thank you for taking the time to report an issue.
What's wrong... Please write below.
when I tried to print again, I was given this run time error 2465.
"Backup and Send a Report".
So, after that I have in my folder database_backup.mdb with 9,75 Mb and database.mdb with 3,9 Mb. Seems to be the same exact database. Same number of records, etc, so why the size is so different
There are a total of four querys in the file but the forth one is the only query that gives me the error message. I have been using this query for about two years and this is the first time this has happened.
No changes have been made to the query and I have plenty of room on my Tb hardrive.
I have included a Access 07 demo database to better view the issue.
While setting up the page size to A4 I'm getting error if printer is not installed. I want to set the page size to A3 whether printer is not installed because Excel Dashboard is generatedin Network drive and from there user will print the dashboard.
Any idea how to set the page size to A3 without installing the printer.
"Microsoft office access has detected that this database is in an inconsistent state"
I cannot open the database what so ever and the size is now 2GB, size compacted is 400mb.
I am using Access 2007, but the database I created is in 2003 format
When I try and change the field size on any text fields, I get an odd error message on saving. It doesn't matter whether I'm increasing or decreasing the size.
"Microsoft Access can't change the data type.
There isn't enough Disk Space or Memory"
Disk space isn't a problem, there's 15gb free on a 27Gb network partition. And my PC is fine, it's a dual core with 2Gb.
If I reduce the size of the text field I get the message that data may be truncated as you would expect, and then the message. There's no way that reducing the size of a field should give that message.
The field isn't linked via a relationship to anything, it's a free text comment field.
I've tried backing up the Db and compacting, as that usually sorts weird errors out, but not this time
If you make an error and change the SIZE, the COMMODITY_NUM will update itself. However, if you made an error to the CLASS and go back to change it after you have already entered a size, the COMMODITY_NUM will not update, and it ends up storing the wrong information. Can someone tell mewhat to do to my code to fix it?
We have read that each db can be up to 2G. So we're not in trouble yet but would like to know:
1) Is there a way to stop the db inflation during the import?
2) What size of db should we start getting concerned over? 1G? 1.6G? other?
3) Will archiving data from the tables (then deleting it) help significantly to reduce the db size?
4) If yes to #3 - is there a way to find the tables causing the biggest useage