Bug 141630 - Crash in: s_stub_releaseInterface FILEOPEN, FILESAVE
Summary: Crash in: s_stub_releaseInterface FILEOPEN, FILESAVE
Status: RESOLVED DUPLICATE of bug 141629
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Base (show other bugs)
Version:
(earliest affected)
7.1.2.1 rc
Hardware: x86-64 (AMD64) Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-04-11 19:28 UTC by daved123g
Modified: 2021-04-11 20:52 UTC (History)
1 user (show)

See Also:
Crash report or crash signature: ["s_stub_releaseInterface"]


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description daved123g 2021-04-11 19:28:17 UTC
This bug was filed from the crash reporting server and is br-d77bf91a-9b3e-4ca0-81f2-57cd4e0b6f2f.
=========================================
Attempted to connect to an existing MSJet (v4) database (MS Access 2003). This database and its VBA front end has run for years on XP, W7 and has just been moved to Win10, where it runs ok after a certain amount of manual tweaking. In its native context the half with the tables runs on a NAS drive and the half with the forms runs on a PC.

The database is in two halves - the tables and the forms: the latter does have a few local tables. Initially I tried connecting the the back end with the main tables and when that failed I tried to connect to the front end, with exactly the same result.

Libre seemed to make the connection ok but fell over when I tried to save the "new" database - possible a problem doing some sort of conversion?

I now want to bring the front end into the 21st centurey and was hoping Libre Office can provide the necessary equivalent to VBA. This is a large, complex database with a large, complex VBA program driving it.

LibreOffice 7.1.2 (2021-04-01) - Fresh Branch
Comment 1 Xisco Faulí 2021-04-11 20:52:37 UTC

*** This bug has been marked as a duplicate of bug 141629 ***