Search results

That is because the time to wait for the connection before aborting the connection attempt is not the business of the ODBC driver but of the calling process. Try to set the LoginTimeout property of the DBEngine, which is the calling process in this context. Of course, this must be done before...

Not yet. It might in the future. Let's hope this will work out.

That's a very secret flavor of SQL. And that's where it is coming from... now hush! Don't stir the Witchmaster General! SCNR

-> INFORMATION_SCHEMA.TABLES, INFORMATION_SCHEMA.COLUMNS

Yes Usually, you would write those just once, make sure they works as intended, and then never touch them again. The advantages are that you can copy the modules containing the functionality to other projects as reusable components and, equally important, that you don't pollute the global...

I don't think this is a good plan. Most API functions cannot be called in a simple and direct way as normal VBA functions but need initialization, prepared buffer, or are only useable in conjunction with other functions. I would rather encapsulate those APIs in their own module, as probably...

Run Compact&Repair and you might notice it no longer gives the same result.

That's probably because the different provider versions have different names. Version 18: Provider=MSOLEDBSQL; Version 19: Provider=MSOLEDBSQL19.1;

@KitaYama , it might help diagnosis to do the following: Create an empty text file, name it: Test.udl Duoble click that file in Windows Explorer. This will bring up the OLE-DB Data Link Manager. There you see a list of all installed OLE-DB providers. The old provider for SQL Server will be...

Beginning a connection string with "ODBC;" is Access-specific for linked tables. I don't think this should be there in any other scenario.

Never heard of them before. I just watched their "Convert MS Access into Web Apps" video and am quite underwhelmed. - They're not converting anything in the video but just completely rebuilding it manually based on an Excel data exported from Access.

This is a weird problem I haven't heard about yet. As your DB works in one folder without those security warnings but not in the other, I would strongly recommend to double and triple check the Trusted Locations in Trust Center.

But it is not covered on your web-page on UserControl. - That's the point I intended to make. Also not mentioned on your web page. You write "This article shows how the UserControl property can be used to restrict how an application can be opened." - Sure, my above points are nor relevant in...

Excuse me? Whether Access prompts to save changes to object designs or not is nothing of consequence? - I beg to differ!

@arnelgp , I cannot find the term IsDirty in the whole Access object library. @isladogs, it would be nice to have some more information on the UserControl property, such as what we figured out here in this thread. The official documentation is woefully sparse.

Just a wild guess: Try setting accobj.UserControl = True @arnelgp , the question was about changes to the design of objects.

The integral part is: Precision - Scale. In your case: 73 - 45 = 28 So, Rule #1 applies! Scale = min(scale, 38 - (precision-scale)) In your case: min(45, 38-(73-45)) = 10

When using DB.Execute, did you use the dbFailOnError option? Otherwise you might not get a catchable VBA error when the query fails. DoCmd.OpenQuery with SetWarnings(False) is even worse in that regard.

Exactly! IIRC this is also officially documented in the T-SQL Documentation. Applying this to the original statement: BEGIN DECLARE @One AS DECIMAL (28,16) = 1, @OneDotNineFive AS DECIMAL (28,16) = 1.95; SELECT CAST(ROUND(@One/@OneDotNineFive,16) AS DECIMAL...

Apparently? You disappoint me Doc. ;-) You're correct, but you usually reference the VBA Language Specification to underpin your statements in such kind of matters. The Set Coercion section of the specification details that the static semantics (compile time) allow any type of object (and...