CLASSICAL MUSIC AND COMPUTER SCIENCE

Oliviero wrote:

If anyone has downloaded one or both of the programs, I would appreciate some feedback: if everything went well, if there were any problems, if there are clarifications to be given or advice to be received. Thank you

Oliviero

the "Discoteca Classica" gives me an annoying problem upon exit:

a pop-up opens that says

"Application execution terminated due to a run-time error

The application will be closed"

I click OK and this reappears continuously, without hope...

i had to "kill" the application with difficulty.

That message, in reality, also appears on other occasions when the program crashes.

That said, yours seems to me a truly excellent piece of work, far too complex and articulated.

As far as I am concerned, it is going in the right direction in the sense that it allows for archiving not so much the disc itself, but the single content, by normalizing it.

I will continue with the tests and update you

thanks and good work

C

Unfortunately, the error you are reporting has never appeared for me. I found another similar report on the Internet but in a different context. I am inclined to think that it is a compatibility problem between the Access 2016 runtime resident on your PC and my program, which should run with the 2003 runtime (which was installed along with my program but is not used because the system gives priority to Access 2016). If you have the Office 2016 installation disc (and you don't have programs in use that run with Access 2016), you could try uninstalling Access 2016 to see if my program (which at that point should run with the installed 2003 runtime) no longer gives the error. If you do this test, however, it would be necessary to remove every reference to Access 2016 from the registry because otherwise I have the impression that the system continues to refer to Access 2016, even if it is no longer there.

I am sorry for this inconvenience, but unfortunately Microsoft does not worry much about the compatibility of its updates with previous versions...

It is a shame that you cannot use it since it would meet your expectations. Let me know. Best regards

Oliviero

Update the software to Access 2016? I mean, after 13 years it is really out of support.

For Carlo

It is my understanding that applications created with Access 2003 should be compatible with the 2016 runtime. I would like to better understand in which circumstances the error appears. You wrote 'upon exiting the program [...] and on other occasions', so I imagine you are able to perform operations (for example, entries) or not?

Another thing: does the MUSICAL ATLAS (which I assume you downloaded) have the same problems?

I await information, thank you

Oliviero

Oliviero wrote:

For Carlo

It is my understanding that applications prepared with Access 2003 should be compatible with the 2016 runtime. I would like to better understand in which circumstances the error appears. You wrote 'upon exiting the program [...] and on other occasions', so I imagine you are able to perform operations (for example, entries) or not?

Another thing: does the MUSICAL ATLAS (which I assume you downloaded) have the same problems?

I await information, thank you

Oliviero

Oliviero... that problem indeed occurs on other occasions as well, but when it occurs upon exiting, I then have to kill the access process with "Task Manager", because clicking "OK" does not clear the popup, as if it were in a loop.

Sometimes it occurs when saving an entry (of a work, or of a new performer) and in that case the error behavior is "normal": I click "OK" and the application stops, but the record is not saved.

However, all of this happens too often—in fact, systematically—and makes the application unusable. In essence, I fear there are compatibility issues, but since I am not a technician, I wouldn't know where to look: I must say that I have also stopped investigating because the problem indeed appears regularly, which precisely makes me think of an incompatibility issue.

I will make a more "functional" comment... your Discoteca application, from what I have been able to see, is perhaps far too complex, in the sense that the fields that constitute a record are too many and there is too much information that can be managed. I would have done something much simpler: author, composition, performer(s) + a notes field for year of recording, label, etc. stop. The setup you provided is substantially this, but there have been many overlaps that make usage (technical problems aside) a bit heavy and entry redundant.

The Atlas, on the other hand, is a colossal work; consultation is easy, the amount of information is remarkable...

Unfortunately, this also gives me, less often but regularly, the runtime problem, which confirms to me that the origin could be "systemic".

Bye and see you soon

C

I hope to find someone in possession of Access 2016 so that I can directly test the highlighted problem and, if possible, find a solution.

Regarding the wealth of data intended for entry into DISCOTECA, the organization stems on one hand from its relationship with ATLANTE (and therefore the possibility of retrieving data from the latter, saving time) and on the other from the need to be able to perform complex searches on one's own disco, something increasingly necessary as it grows.

I am sorry for this inconvenience that prevents its use. If I were to solve it, I would like to have the opportunity to let you know.

Talk to you soon.

For Carlo:

I involved an Access expert friend who suggested a test that you could perform. The purpose is to force the execution of my programs using the 2003 runtime, which was installed along with my programs, instead of the 2016 runtime that uses Access 2016 when an MDB or MDE file is launched.

I have put two batch files on Google Drive (prova_AM.bat for ATLANTE and prova_DC for DISCOTECA) to perform the test: you should download them, place them in their respective directories containing the programs, and then launch them with a double click. If everything goes smoothly, a black DOS window should open and then my program should start, which should be executed by the 2003 runtime that was installed along with my programs, so you can then check if the errors still appear.

Below you will find the content of the two batch files:

Text for ATLANTE:

if %PROCESSOR_ARCHITECTURE%==x86 (
rem 32 bit
"%programfiles%\Microsoft Office\Office11\msaccess.exe" "%CD%\AM.MDE"
) else (
rem 64 bit
"%programfiles(x86)%\Microsoft Office\Office11\msaccess.exe" "%CD%\AM.MDE"
)

Text for DISCOTECA:

if %PROCESSOR_ARCHITECTURE%==x86 (
rem 32 bit
"%programfiles%\Microsoft Office\Office11\msaccess.exe" "%CD%\DC_COPERTINE.MDB"
) else (
rem 64 bit
"%programfiles(x86)%\Microsoft Office\Office11\msaccess.exe" "%CD%\DC_COPERTINE.MDB"
)

ATTENTION: you must first verify that MSACCESS.EXE is present on your PC under the \OFFICE11 directory.

If you would be so kind as to try this, let me know the result.

It's been a lifetime since I last saw Batch. I'm getting emotional. I used to have fun writing viruses with it as a child. Such beautiful memories...

Oliviero wrote:

For Carlo:

I involved an Access expert friend who suggested a test you could perform. The goal is to force the execution of my programs using the 2003 runtime, which was installed along with my programs, instead of the 2016 runtime that uses Access 2016 when an MDB or MDE file is launched.

I have put two batch files on Google Drive (prova_AM.bat for ATLANTE and prova_DC for DISCOTECA) to perform the test: you should download them, place them in their respective directories containing the programs, and then launch them with a double click. If everything goes smoothly, a black DOS window should open and then my program should start, which should be executed by the 2003 runtime that was installed with my programs; then, check if the errors still appear.

Below you will find the content of the two batch files:

Text for ATLANTE:

if %PROCESSOR_ARCHITECTURE%==x86 (

rem 32 bit

"%programfiles%\Microsoft Office\Office11\msaccess.exe" "%CD%\AM.MDE"

) else (

rem 64 bit

"%programfiles(x86)%\Microsoft Office\Office11\msaccess.exe" "%CD%\AM.MDE"

)

Text for DISCOTECA:

if %PROCESSOR_ARCHITECTURE%==x86 (

rem 32 bit

"%programfiles%\Microsoft Office\Office11\msaccess.exe" "%CD%\DC_COPERTINE.MDB"

) else (

rem 64 bit

"%programfiles(x86)%\Microsoft Office\Office11\msaccess.exe" "%CD%\DC_COPERTINE.MDB"

)

ATTENTION: you must first verify that MSACCESS.EXE is present in your PC under the \OFFICE11 directory.

If you are so kind as to try this, let me know the result.

Oliviero, I tried it this way too, but the runtime error appears regularly... unless it is an operation that I am somehow doing incorrectly, but in any case, it means that some check is being bypassed...

Bye and thanks anyway

C

MESSAGE FOR CARLO:

I have discovered the cause of the runtime error in the DISCOTECA CLASSICA program, an error that only occurs if the user does not establish a connection with the ATLANTE. I have now modified the code so that the error no longer occurs even without the connection between the two programs. I have uploaded the updated package to Google Drive, but I have also included the standalone program (DC_COPERTINE.MDB) which can be downloaded and used to replace the previous one for those who have already installed the 2003 runtime.

MESSAGE FOR THE ADMINISTRATOR:

Since it is likely that our friend from Brescia will no longer consult this section of the Blog (having given up using the program), I am asking if it is possible to notify him of this update via email.

Thank you

Oliviero

Oliviero, you can also send a private message... which I imagine triggers an email notification to the user (unless they have disabled it).

Exactly...

Oliviero wrote:

MESSAGGIO PER CARLO:

I discovered the cause of the runtime error in the DISCOTECA CLASSICA program, an error that only occurs if the user does not establish a connection with the ATLANTE. I have now modified the code so that the error no longer occurs even without the connection between the two programs. I have uploaded the updated package to Google Drive, but I have also included the standalone program (DC_COPERTINE.MDB), which can be downloaded and used to replace the previous one for those who had already installed the 2003 runtime.

MESSAGGIO PER L'AMMINISTRATORE:

Since it is likely that our friend from Brescia will no longer consult this section of the Blog (having given up on using the program), I am asking if it is possible to notify him of this update via email.

Thank you

Oliviero

Hi Oliviero

i see your post now

i am a bit busier with work during this period, but I will try to run some tests with the new software release

see you soon and thanks

C