Search results

Thanks will do. I assume I can't be the only person this will happen to.

Some are on the users' own PCs. Some are on the shared drive. Normally all would be on one or the other but I'm experimenting to see if it makes a difference and the change is negligible.

Thanks, I'll try it

I've found various questions about Access speed over a remote connection but can't find one that quite covers this problem. Apologies if I've missed it. Until two weeks ago, we had a load of databases on a shared drive (P:\). They were set up with a shared back end and each user having their...

Sorry, should have added that to the list of things I tried. The connection string generated by Access looks the same as the one in the code.

Thanks all. 1. Will change the declaration and see if that helps. 2. haven't used the Event Viewer before. Will look into it. 3. Yes, just the database name is given, no file/system/ etc. This was set up before I got here and has been running fine for years.

Our company just upgraded everyone from Access 2010 on a Windows 7 device to Access 2016 on a Windows 10 device. One of the problems encountered is as follows, but only happens to one person, which has me puzzled. There is a line of code in a few of the databases that uses a global password and...

Sorted! The problem turned out to be that only the 32 bit Access drivers were installed (no idea why). I downloaded and installed the 64 bit and Access showed up as it should. I was then able to connect in Qlik View. Thanks so much for the help, it pointed me in just the right direction.

It's 64 bit. Professional Plus 2016. However, when I go via the 'ODBC Data Source Administrator (64 bit)' dialog and select 'MS Access Database (which shows both *.mdb and *.accdb as options), only 'SQL Server' is available in the 'Create New Data Source' dialog.

Yes, in step 4 I changed the file type to 'All Files'. After that, I could see the accdb file I want. I (perhaps incorrectly) assumed I could do this, as the earlier screen showed *.mdb and *.accdb as options?

Thanks for the reply. Yes, I have Access installed and I created a small database to use for testing (just one table).

Does anyone have any experience of adding a driver for accdb files under Windows 10? I'm testing out Qlik View with Access which means, for the first time, I'm trying to install a 32-bit driver on my home PC. The steps I used were as follows: I open the Control panel I click on 'Set up ODBC...

....aaaaand there's our current problem. We have permission to go into salesforce and run reports. Nothing else. I'm coming to the end of a two year battle that's resulted in them exporting a load of data for us on a daily basis, creating a few CSV files which I then import at our end, just so...

Thanks CJ. It's the multiple sources bit that my manager noticed. We use Salesforce in conjunction with other sources and it would be nice to access the data directly.

Thanks, Minty. That's my impression so far.

I was wondering if any of the esteemed users on here have had any experience of using Qlik View with Access or other dbs? I've been informed that my department has a few Qlik View Server licenses, we're just not currently using them. My manager is toying with the idea of me getting a Qlik View...

We had this issue just after I came here. Everyone was running Office 2003 and they upgraded to 2010. The various databases had been built not only with the front and back ends in one file but with everyone accessing the same file to do work. The first time someone who'd been upgraded to 2010...

You may be right, but that's a little above my authority. Everyone here gets it.

Thanks. I split everyone out into their own front end a while back, so that's covered. The other Office items (word, excel ppt and outlook) are already at 2016, they held off on Access. Back when they jumped from 2003 to 2010, the references caused a few headaches. this is why I'm wary about...

Our IT department has decided that the whole company is to upgrade from Access 2013 to 2016. Unfortunately, this will be done over a 7 - 10 day period, meaning that some people will be running 16 while others are still running 13. Everyone has their own front end file, so the fact that the...