bobjackson
Programmer
Help !!!
The database that I am currently running has just come back with this error on one of the records.
The database set-up is Back-End / Front-End.
The index table has 219 fields in it. Which I know is why I have got the problem, I now need to look at splitting the table into several smaller ones.
I currently have 9 fields that record changes to specific fields i.e. oldvalue. Maybe I could move these into one table for tracking purposes along with the new value and recordid.
There is another 19 fields that I could possible move out , but the issue I have is if I create a new record do I need to write some code to get the database to create the record in both tables.
How far do I have to go (i.e. how many fields is it wise to move into another table.)
Never smile at work, they may think you're enjoying yourself too much and cut your pay.
The database that I am currently running has just come back with this error on one of the records.
The database set-up is Back-End / Front-End.
The index table has 219 fields in it. Which I know is why I have got the problem, I now need to look at splitting the table into several smaller ones.
I currently have 9 fields that record changes to specific fields i.e. oldvalue. Maybe I could move these into one table for tracking purposes along with the new value and recordid.
There is another 19 fields that I could possible move out , but the issue I have is if I create a new record do I need to write some code to get the database to create the record in both tables.
How far do I have to go (i.e. how many fields is it wise to move into another table.)
Never smile at work, they may think you're enjoying yourself too much and cut your pay.