Excel Crashing
-
Is it happening on every user, or just one user? Is it happening with Excel open on a blank sheet, or is there a specific sheet that is causing the crash? If it is a specific sheet, does it include VBA?
-
So it happens for multiple users so far...randomly and yes the Excel queries an Access database and I believe has VBA tied in. It's a huge database they work from.
-
@Joel said in Excel Crashing:
So it happens for multiple users so far...randomly and yes the Excel queries an Access database and I believe has VBA tied in. It's a huge database they work from.
This is going to be just a rational person saying this, but why is the business using Access, to run a "huge database"... If it's that large, it should be run on a proper database platform.
Now I'm guessing converting the system say SQL or SQLExpress or MySQL is out of the question, correct?
When did this issue start occurring, around the time of the OP creation? Has there been any changes to the VBA, how large of an Access database are we discussing.
How many users attempt to access this system concurrently?
-
@Joel said in Excel Crashing:
So it happens for multiple users so far...randomly and yes the Excel queries an Access database and I believe has VBA tied in. It's a huge database they work from.
Oh, this is likely the JetDB (there is no such thing as an Access database, Access is the front end, not the database, Access bundles with JetDB for testing use and uses SQL Server for real use.) JetDB is not meant to handle anything large, multiple users or production use. It is probably something to do with this because that's extremely fringe use case.
Any chance of moving that to SQL Server?
-
@DustinB3403 said in Excel Crashing:
Now I'm guessing converting the system say SQL or SQLExpress or MySQL is out of the question, correct?
Probably, or they would have. But I'm interested to know why, as I'm not aware of any situation where JetDB is functional or possible, that SQL Server Express can't do it for free. But there must be some functional difference somewhere, I'm guessing.
-
@scottalanmiller said in Excel Crashing:
Oh, this is likely the JetDB (there is no such thing as an Access database, Access is the front end, not the database, Access bundles with JetDB for testing use and uses SQL Server for real use.) JetDB is not meant to handle anything large, multiple users or production use. It is probably something to do with this because that's extremely fringe use case.
Cool didn't know that.
I've heard of Jet DBs before, but didn't put two and two together.
-
@scottalanmiller said in Excel Crashing:
@DustinB3403 said in Excel Crashing:
Now I'm guessing converting the system say SQL or SQLExpress or MySQL is out of the question, correct?
Probably, or they would have. But I'm interested to know why, as I'm not aware of any situation where JetDB is functional or possible, that SQL Server Express can't do it for free. But there must be some functional difference somewhere, I'm guessing.
I'm guessing that whoever made the JetDB a while ago never thought it would be used like this or this long so the thought of moving it to SQLExpress hasn't been thought of.
Also, nearly anyone can setup an Access created JetDB, but those same people probably have no clue how to transfer it into a SQLExpress
-
@Dashrender said in Excel Crashing:
Also, nearly anyone can setup an Access created JetDB, but those same people probably have no clue how to transfer it into a SQLExpress
Pretty sure that it is just a check box when setting up your Access application.
-
@scottalanmiller said in Excel Crashing:
@Dashrender said in Excel Crashing:
Also, nearly anyone can setup an Access created JetDB, but those same people probably have no clue how to transfer it into a SQLExpress
Pretty sure that it is just a check box when setting up your Access application.
It sure is. That's like the only thing I have to remember when installing Access here (we're all SQL).
-
@scottalanmiller said in Excel Crashing:
@Dashrender said in Excel Crashing:
Also, nearly anyone can setup an Access created JetDB, but those same people probably have no clue how to transfer it into a SQLExpress
Pretty sure that it is just a check box when setting up your Access application.
I haven't created an Access created DB since Office 2007 or was it XP? I'm guessing that checkbox is new (to me).
