Build Fails - Error 32582

[Saffer70]

Just started trying this out last week. Great addin, well done!.

Ran into this issue, see log below. The error suggests to change the sort order, but cant find it anywhere. Using the 365 version 2410 build 16.0.18129.20100.

Thanks!

---

Beginning Build from Source
Solution Notification V9.5 Next Up.accdb
VCS Version 4.0.34
Full Path: C:\Users\lax-andreu\Desktop\Solution Notification\Solution Notification V9.5 Next Up.accdb
Source Folder: C:\Users\Andre\Desktop\Solution Notification\Solution Notification V9.5 Next Up.accdb.src
10/29/2024 5:39:31 PM

---

ERROR: Unhandled error, likely before On Error directive
Error 32582: The specified file name could not be used to create a database. Specify a different database name. Source: .Unknown.LogUnhandledErrors

This may occur when building an older database version if the 'New database sort order' (collation) option is not set to 'Legacy'

---

            PERFORMANCE REPORTS

---

Operations Count Seconds

Console Updates 2 0.01
Create new database 1 0.00
Read File 1 0.00
Parse JSON 1 0.00

Other Operations 0.08

[joyfullservice]

@Saffer70 - Look for something like this in Access options:

[Saffer70]

@joyfullservice Thanks Adam, how did I even miss that!

Confirmed that it is set to General - Legacy. If I read the help correctly, that is what it should be set as. Any suggestions?

[Saffer70]

@joyfullservice Update, I ran a clean build from source on a new .accdb from my office machine this morning on the same git branch, it built just fine. Sort orders are the same on this vs my home machine.

The only difference, my machine at work is Access for office 365 V 2408 build 16.0.17928.20114 whereas my version at home is 16.0.18129.20100.

[joyfullservice]

Interesting... Sorry, I don't have access to the newer versions of Microsoft Access to test, but it sounds like it "should" build fine on both machines if they have the same options specified. I know there have been some bugs in newer versions of Access, but I am not sure if this could be a factor here.

You might try some further testing to narrow down the issue. For example, create a simple test database, try exporting and building that one. If that doesn't work, maybe try one in a newer database format. Sorry, I know that's probably not a whole lot of help, but it might be the best route to try to pinpoint the issue...

[Saffer70]

Thanks Adam, I was going to start doing that last night but ran out of steam. I will do this soon and provide more feedback as I narrow it down,

[hecon5]

@Saffer70 did you figure more info out about this?