"File not found" error (Error 53) when opening Access database
I'm getting a "File not found" (Error 53) error when trying to open an Access database (.accdb file). The error appears during the database startup process and points to a VBA subroutine declaration line: The error message mentions "The file was not found where specified" which suggests VBA is looking for a file during project compilation, but I can't identify what file it's looking for. Has anyone encountered this issue where the same Access file works with some SQL Server backends but fails to even open with others?MS Access Database Decommissioning
Hi folks, We have the following version of the MS Access Database and we are not sure when MicroSoft is decommissioning this version of MS Access Database. We have the latest version of MicroSoft Application installed as a part of our environment, but the actual MS Access Database is the following for one of the databases. Do we need to update this database called Pontiac to the latest version of database. The database itself is showing Access 2007-2016 file format - Access. Do we need to update this database to the latest version of database. We really appreciate your recommendations. Thank you
Problems with navigation pane on word 2021 - constantly slowness and freezing
Hello, everyone. My name is Diogo. This is my first post. I just bought Office 2021 home version today. I've been using 2013 Office version for a long time and decided to upgrade. The main reason was my daily use of a word doc for studying purposes. The doc is long (at least from my perspective), with sth abou 3100 pages and 1.4 million words. With 2013' version, I had basically two issues when using this file specifically 1. Sometimes when I was saving the file and, before the end, it was shutted down without properly save (I guess this one is done with 2021's autosave option). 2. The navigation pane (titles and search specifically words) was incredibly slow sometimes. In fact, it was almost impossible to open the titles and digit the text at the same time, so I had to keep it on the search columm to keep working the text. The search columm, besides that, used to freeze after a search for 10 seconds, max 15 seconds, maybe, but after I could keep the work progress and typing Well, I bought the 2021 one thinking that would be faster and I would solve this problem, but it is not my experience so far. The overall use is better with this newer version, but it's (much) worse to search words with navigation pane, which is very useful in my daily use of the doc. When the titles panel is open, everytime I digit it freezes a little bit, making harder to use. When I search for a word, it definitely freezes, taking sth about 25, 30 seconds to come back, when it will keep freezing for a while. In simples words: when it comes to use the navigation pane (titles and search, I never use pages miniatures), Word 2021 is, so far, much worse than 2013 Office. The office keeps freezing sometimes, even not using the navigation pane (sth I was not expecting buying this Office 2021, to be honest), but the situation is worse with navigation pane, like I said. P.s. I've been editing this file for 18 months now. At some point and for some reason I can't tell, the automatic numbering option (sorry, I use in portuguese and I don't know the name Microsoft uses in english Word version, but it's on the paragraph tab and allows to divide paragraphs in numbers and letters. I guess it's numbered list or sth similar) stopped working, so I started mumbering everything manually. I don't know if this could be interfering. P.s. 2 Before come here I contacted Microsoft via chatting. He tryed to help me, controlling the PC remotelly and doind some tricks, but at the end he sad it was probably some formatting problem with this precise doc file, so he directed me to his forum Sorry about the long text and thank you for the help Diogo
MS Access Handling Nulls In Query Formula
Hi all, I have this formula in Access: IIf([Init_Static_P] < 0 And (Nz([Adj_Static_P], -9999) < 0), "Resolved", "Not resolved" which keeps outputting an #Error when Adj_Static_P is null which will happen. I need the nulls in my dataset. Whenever Init_Static_P is < 0 and or Adj_Static_P is < 0, it works as it should outputting "Resolved" and vicer versa, however it does not work whenever there is any instance of Adj_Static_P as a blank value. Does anyone know how I can handle the nulls so that if the Init_Static_P is >0 and Adj_Static_P is null, then it would output "Unresolved", and if Init_Static_P is <0 and Adj_Static_P is null then it would output "Resolved" instead of #Error? Output should be as follows: Init_Static_P Adj_Static_P Result >0 Null "Not resolved" >0 >0 "Not resolved" <0 Null "Resolved" <0 < 0 "Resolved" Thanks in advance! <3ODBC --call failed. [Sage][Support] (40190) Data conversion algorithm not supported for...
ODBC --call failed. [Sage][Support] (40190) Data conversion algorithm not supported for SQL_BIT to SQL_TYPE_DATE. (#40190) I'm trying to execute an update statement in MS Access using the following, but keep getting an error message: Any ideas what I'm doing wrong here? Appreciate any feedback.
ADODB performance problem
Hi All, (Win10, Win11) To highlight a performance problem (with ADODB/ACCESS), on a heavy client, I wrote two small programs one in VB.NET (and VBA), the other in CPP/MFC. Using the same component (msado15.dll). This piece of code does nothing but connect to two ACCESS files (with a single table of 15,000 records), and via a recordset copy from one database to the other. Under VB.NET, it takes 1 second. Under CPP, on a machine that has the runtime access 2013 x64, it takes 9 seconds. (i spend 99% of my time in AddNew() )... Under CPP, on a machine that has the runtime access 2016 x64 OR Office365, it takes 20 minutes. (i spend 99% of my time in AddNew() )... The target computer must have Office365... I need an issue... PS : My two sln (exe/cpp/...) are available...There is no sensitive data... A short running test... |Nom de la fonction|Total \[unit, %\]|Self \[unit, %\]|Nombre d'appels|Module| |-|-|-|-|-||*+*D:\\users\\phili\\Downloads\\Test\_ADO\_Cpp\_VB\\test\_minimal\\x64\\Release\\test.exe \(PID : \)|115,73s \(100,00*%\)|0ns \(0,00*%\)|0|Plusieurs modules| |\|*+*\_\_report\_gsfailure|115,73s \(100,00*%\)|9,20?s \(0,00*%\)|1|test| |\|\|*+*\_\_scrt\_common\_main\_seh|115,73s \(100,00*%\)|13,20?s \(0,00*%\)|1|test| |\|\|\|*+*main|115,73s \(100,00*%\)|654,83ms \(0,57*%\)|1|test| |\|\|\|\|*-*\[Native\] msado15.dll!0x00007ffe8947bc40|104,82s \(90,58*%\)|104,82s \(90,58*%\)|6215|msado15| <= AddNew() !!! |\|\|\|\|*-*\[Native\] ucrtbase.dll!0x00007fff373ccad0|9,31s \(8,05*%\)|9,31s \(8,05*%\)|1|ucrtbase| |\|\|\|\|*-*ADODB::Connection15::Open|413,29ms \(0,36*%\)|8,80?s \(0,00*%\)|2|test| |\|\|\|\|*-*\[Native\] msado15.dll!0x00007ffe8947c010|101,83ms \(0,09*%\)|101,83ms \(0,09*%\)|2|msado15| |\|\|\|\|*-*printf|96,90ms \(0,08*%\)|157,30?s \(0,00*%\)|214|test| |\|\|\|\|*-*\[Native\] msado15.dll!0x00007ffe8947d3d0|91,69ms \(0,08*%\)|91,69ms \(0,08*%\)|74568|msado15| |\|\|\|\|*-*\[Native\] msado15.dll!0x00007ffe8947d380|50,46ms \(0,04*%\)|50,46ms \(0,04*%\)|74568|msado15| |\|\|\|\|*-*\[Native\] msado15.dll!0x00007ffe894d8fc0|30,92ms \(0,03*%\)|30,92ms \(0,03*%\)|149136|msado15| |\|\|\|\|*-*\[Native\] msado15.dll!0x00007ffe8947bfc0|28,68ms \(0,02*%\)|28,68ms \(0,02*%\)|6214|msado15| |\|\|\|\|*-*\[Native\] combase.dll!0x00007fff39403f10|26,94ms \(0,02*%\)|26,94ms \(0,02*%\)|5|combase| |\|\|\|\|*-*\[Native\] msado15.dll!0x00007ffe89513fc0|17,39ms \(0,02*%\)|17,39ms \(0,02*%\)|149137|msado15| |\|\|\|\|*-*\[Native\] msado15.dll!0x00007ffe894c1480|15,11ms \(0,01*%\)|15,11ms \(0,01*%\)|1|msado15| |\|\|\|\|*-*\[Native\] msado15.dll!0x00007ffe8947c230|14,46ms \(0,01*%\)|14,46ms \(0,01*%\)|149137|msado15| |\|\|\|\|*-Native\]msado15.dll!0x00007ffe8947d2b0|11,32ms\0,01*%\)|11,32ms\0,01*%\)|149136|msado15| Regards
