[RESOLVED] Having trouble trying to 'acknowledge' new version of a table.

[Wahreez McDermott]

I downloaded the newest version of Pinball X Database Manager. I hadn't touched the software in roughly two years, but after updating everything appears to work properly.

The one issue I am having is that when I update a table with the newest version I am still continually getting "New Version available" when I restart the Pinball X Database Manager.

I tried using the 'acknowledge' button, but that gives the following error...

ERROR INFO    :    Datetimereformatstring2date    String '2025-01-17 18:13:28 23:59:59' Was Not Recognized As A Valid Datetime.
ERROR INFO    :    Backnowledge_Click    Conversion From String "" To Type 'Date' Is Not Valid.

I managed to work around the issue by opening the table and making a small meaningless change and then saving it so that I no longer get an update notification, but that's not a proper fix.

Thanks for your help! I think it has something to do with the "Last Spreadsheet Date" which is listed as 2025-01-17 18:13:28 23:59:59 in the log file.

I don't know how to fix it though.

Edit: I have all my tables in \Visual Pinball\Tables\VPX

[Mike_da_Spike]

We appreciate you reporting this issue.

Please provide your complete DatabaseManager log file and the config file as attachments.

Additionally, please provide your Windows language and locale settings to facilitate accurate reproduction and resolution of the reported issue.

[Wahreez McDermott]

My Windows language is English and I live in Texas.

DBManagerLog.txtFetching info... PinballXDatabaseManager.iniFetching info...

Thanks!

[scutters]

  On 3/2/2025 at 10:32 PM, Wahreez McDermott said:

My Windows language is English and I live in Texas.

DBManagerLog.txt 3.53 kB · 1 download PinballXDatabaseManager.ini 2.5 kB · 0 downloads

Thanks!

Expand  

Thanks. It is indeed a bug!, looks the format of dates from vpsd has changed at some point causing the issue (no idea when). Will be fixed in the next release.

[Wahreez McDermott]

Thanks!

[Mike_da_Spike]

This is fixed in release 25.03.17