Recent content by amorosik

This project is truly spectacular. A perfect example to bring to the attention of those who persist in viewing the Microsoft Access development system as a simple form and report builder. Congratulations, great work.

And how do you send them all together to the Claude system? And can Claude 'understand' the program flow?

What you mean exactly "..which has a copy of my whole project as text files.." ??? You have exported all the objects contained in an Access project using tools like vcs-access ? And can you have them analyze a project composed of hundreds of files?

Copied the contents of modVariabiliGlobali to a text file Deleted the modVariabiliGlobali module Compacted the project Created a new module, named modVariabiliGlobali2 Pasted the contents of the text file into the new module Now debug/compile correctly Access probably somehow 'marked' the module...

Hi Mario, we use a Custom Kube with thermal paper, and for full cut/partial cut paper, on properties of printer driver, we have CUT MODE

"...a list of globals like that..." Exactly, what list of global variables wouldn't be a very serious design flaw?

Good question Yes, on other modules, for example modFtpServer module, the intellisense show all vars expected Wait a moment, if i write modVariabiliGlobali.gbDebug the variable is correctly recognized, if i write gbDebug si not recognized As if gbDebug was a public member of a class module...

Checked But gbDebug (like other public vars) is defined only on modVariabiliGlobali

I exported manually by going over the module and right-clicking, then selecting Export to Text File The result is shown below At first glance, it doesn't seem like anything special. Attribute VB_Name = "modVariabiliGlobali" Option Compare Database Option Explicit 'Public sFiles() As String...

"First time" indicates the first time I try compile after the project has been imported from text files "..Do you import into a newly created blank Access file .." Yes

Thanks for the suggestion But I just tried importing all the objects from a text files, and the first time I try to compile it, it gives me the problem of undefined variables I absolutely have to continue using the project as before, before exporting/importing, otherwise it won't work properly...

Yes, on a standard module On modVariabiliGlobali threre are only variables, no procedures, no functions

This is what I did. All global variables are defined within the standard modVariabiliGLobali module and are in the form "Public gbDebug As Boolean" But if I try to use gbDebug in other forms/modules/report/class, the code doesn't seem to recognize them. (All modules have the Option Explicit line)

I have a project created with Access 2013, 32-bit I normally use this procedure to export the entire project to a text file and archive it (VCS_ImportExport.bas / ExportAllSource) After the last export, I also followed the reverse procedure, and then tried recreating the project from the newly...

Yes, for me too, the main use is on SQL queries. From a formal point of view, the queries are created correctly, and this makes the creation of complex queries much quicker.