Search results

That's great confirmation about using the accdb files. In this COVID mess I've been restricted to using TeamViewer, and while it's a great thing, it's no substitute for just keeping an eye out for when users are available and checking their versions, so my 'feel' for the overall office...

Sorry to keep replying to my own posts, but I found a note from DocMan which made me question whether sending out accde files was a good idea, so I've dropped back to sending the accdb and I'll see if that works. Jack

Found it - I looked here a dozen times and didn't see it. File / Account / About Access, then in tiny print at the top at the end of the version/build number is says 32-bit. So looks like an upgrade for some users and not for others - ew. That just makes it worse. It would be ok if they were in...

Sorry, but where do I look for the bitness of my Access 365 version? I've hunted high and low - I just assumed it was 64 bit but a client got the following message after opening my new app: "this version was configured for a 32-bit version of access". Any clues would be appreciated...

Thanks Minty, I in fact took your advice, got myself an Azure database, bustled through all the connection stuff, did an hours ETL to fill with data and hey presto, the goldarn application runs like a dream. So armed with that information I've fronted up to the DBA and did a 'ploise exlpine'...

As far as I know, it's in an Azure environment.

Hi, I have an Access 365 FE with a SQL Server Express backend. It works fine in test on my machine (which has both FE and BE). FE is 4mb, backend has half a doz fact tables with 2-300 records in each. I've migrated the SQL to the client's (cloud) server, and connected the FE to it from the...

DBGuy, I'm using 365. Isla, I started down the rabbit hole of code signing because I trialled SSE Setup the other day, and it has a big chunk of information on code signing, all doubtless relevant and important. But the installs I do aren't delivered over the web (they are all custom products)...

Thanks all, very much appreciated.

Here I am again, sorry folks, picking your brains ... I was looking into getting my code signed, and found a few CA vendors like Comodo and DigiCert and was considering signing on the dotted line when I found this...

Hi DocMan, good points which I will follow up. I rather suspect the notebooks might be a little weedy, although if they aren't docking them and they are reliant on wifi, that can be woeful (wofi haha - ahem). Thanks.

Thanks, if I reply in a state of euphoria, you'll know it worked. Silence will indicate grim determined persistence and black coffee.

I'm guessing that if you specify 'open exclusive', Access will be able to bypass all its locking and 'who's using what' code when opening and closing forms. And if so, perhaps it impacts speed? Frankly, I'd be surprised if it made much of a difference, but equally frankly, I haven't encountered...

Hi folks, I have distributed split databases for clients over a number of years, with front ends always deployed to each users C drive, and optimised in fairly standard ways that you'd all be familiar with. In the present case, I am deploying to users with weedy little notebooky things that are...

JHB's answer is correct. Your .Close is closing the database object, so the recordset could not be created. Jack

Hehe so it is. Bit of time travel never goes astray ...

Hi ShanVel, Three guesses: 1) The recordset is somehow set to EOF when you try the second export. In other words, you run the Preview and see records, and then you run the Excel export and no records appear. If you close your app, then reopen and do the second export immediately, does it work...

I'm so sorry about this, but what I'd like is a free ODBC driver for an OData source. How embarrassing, and yes I'd also like cheesecake, coffee (cap with 1), volume 2 of Stalin by Stephen Kotkin, some new golf clubs and a new car to put them in, but the driver would save me quite a few...

Replace this: Set MyDatabase = CurrentDb On Error Resume Next With MyDatabase .QueryDefs.Delete ("tmpOutQry") Set MyQueryDef = .CreateQueryDef("tmpOutQry", strSQL) .Close End With 'Step 3: Open the query Set MyRecordset = MyQueryDef.OpenRecordset with this On Error goto myErrorTrap Set...

Hi Jacek, AFAIK Access will not reclaim space, so both 1 and 2 are going to cause bloat if you are importing millions of records. 3 is a better option. CJ's suggestion is a good one, which I have used to good effect, and is pretty straightforward and easy to implement. But there is another...