Search results

I have a front end database that I've used since about 2002 (in .adp format back in those days) We recently migrated it from 2010 to Office 365 so of course that meant migrating from .ADP to an .ACCDB via Linked tables so we migrated to ODBC linked tables. The SQL backend was 2008 at the time...

I have an Outlook 365 .accdb that i link tables to an old 2008 R2 Windows 2008 SQL machine using Trusted authentication via our Active Directory Connection string was DRIVER=SQL Server;SERVER=10.10.10.50;Trusted_Connection=Yes;APP=Microsoft Office;Network=DBMSSOCN We are in the process of...

I have been an access developer for a very long time, I have a back end database on a QNAP file server 192.168.1.10. I have always connected to that back end using some VBA code with local machines on a FLAT VLAN 192.168.1.0. So imagine my annoyance when i go to connect to that database at an...

Hi I have some code I use to move a form to a third monitor (if one exists) and everything works correctly except the math calculations based on screen size. intMoveX = 86000 If GetMonitorId > 2 Then 'move to monitor 3 and maximize! (getmonitorid also populates the monitorid array public var...

Hi everyone, I'm a long time Access developer and I'm migrating an .adp over to a linked table .accdb with a MSSQL backend. No big deal on the actual import of modules/forms/reports and I linked all the tables (althought it names every table dbo_[name of table] which is kind of annoying but Ill...

So I have an access runtime project that I deploy out, it runs on the 2016 RTE I get errors with Left() functions and I just know its a tell tale sign of .dll versioning problems because other parts of the software runs fine its not that a .dll or .ocx is flat missing. Customer has No full...

Long time access developer started out with 2000. Over the years I've deployed my app with the runtime via the product actual installer to copy the front end backend and assets. I've steadily updated the version over the years, and fought with bitness, I cannot upgrade to 64 bit due to legacy...

Client Verison: 16.0.12430.20264 Office 365 CTR 32BIT My Version: 16.0.4266.1001 Office 2016 32 BIT When I deploy the .accdr basic string functions fail hinting to me there are DLL versioning problems somewhere. What can I do? I've been developing with access for a decade plus and this sort...