I'm getting a bit frustrated with Access. I have set up a number of different machines using Windows 7, 8, 10, on a domain, off a domain, laptops [3 so far], desktops [4 at this point] but all Access does for me is crash. On my last build that I did on my laptop, I made sure that I installed Office last after SQL server and VS 2015/2017 but I still have the same results. Fire up a wizard will be instant crash. Download a template from Microsoft and it won't even give me an error message - just crash. I did noticed that on my new laptop I am able to import data [once] before it will crash but it is guaranteed to crash if I look at it funny. It doesn't matter what the hardware is. My desktop at home runs an AMD ryzen 1700X and all of my laptops have been Intel i7 as well as my work desktop. The last time I've been able to use Access regularly was Office 2010. Currently running the latest version of Office 2016/365
How do you all set up a new machine with Access?
Do you all use SQL server on the same box? If so, is it the full install with SSIS, SSAS, SSRS? This has happened to me with SQL 2012, 2016. Can't remember it being an issue with SQL 7 -2008R2
How about Visual Studio? If so which version? I've been known to have 2008-2017 on the same box.
What other software do you run on the same box?
All of my machines are set up with SQL first in mind since my job is working on large* databases in both OLTP [relational] and OLAP [Cubes/Warehouse]. My desktop has 6 drives, half are SSD and 48 GB of ram. My newest laptop has 32 GB of ram and two hard drives but it will crash just the same.
On my wife's laptop and work desktop, I can use Access without any issues at all but she won't let me install SQL server on any of her machines to test my theory no matter how often I ask. I even offered extra back rubs, more time driving my convertible and tried my famous puppy dog eyes.
I'm thinking that since this has happened to me on install after install, it has to be something that doesn't play well with my other tools.
*The concept of large databases is a moving target. I use to think of a 1 GB database and a hundred thousand rows as being huge. Now that is almost cute. For a weekend project, I imported a trillion rows into a database. For fun. It's a sickness. Most of the time my data that I work with is around 600 GB and 1 TB