Automatic release of documentation. Accounting, storage and circulation of documents in a medium-sized enterprise. What tools do you use?

Question

Automation

Good day, gentlemen. I do not work in the IT field, but recently I have become very interested in the issue of automating office workflows. The essence of the work of my department is the conclusion of various, but the same type of contracts. I decided to create a database in Microsoft Access and use VBA to display data from the database into the necessary text document templates. As a result, it turned out well: I have a database with a convenient account of customers (all the necessary information in one form), plus automatic creation of a package of documents. But now, when the database has grown to almost one and a half gigabytes, it works, to put it mildly, extremely tightly. Based on the information that I got acquainted with, I decided to move to the SQL base. This is where questions arise. After transferring data to SQL Server, many of the field formatting functions become unavailable, at least in the form in which they were available in Access. Is it possible that the database will be stored and processed on the server, and as a client I will use Access, as before? There is a lot of information about this, but it says everywhere that the language of interaction with the database is only SQL. I'm in a strained relationship with access, but here ...) Maybe someone worked with large databases in access? What should I do if I really don’t want to change the client part... If someone has come across such issues, please tell us in more detail, if possible, what course of action to choose in this situation and what time to start learning?) but it says everywhere that the language of interaction with the database is only SQL. I'm in a strained relationship with access, but here ...) Maybe someone worked with large databases in access? What should I do if I really don’t want to change the client part... If someone has come across such issues, please tell us in more detail, if possible, what course of action to choose in this situation and what time to start learning?) but it says everywhere that the language of interaction with the database is only SQL. I'm in a strained relationship with access, but here ...) Maybe someone worked with large databases in access? What should I do if I really don’t want to change the client part... If someone has come across such issues, please tell us in more detail, if possible, what course of action to choose in this situation and what time to start learning?)
Many thanks in advance for any information.
PS: I apologize for the possibly amateurish explanation. How could you guys?)

Answer 1

Access works with the database via ODBC, and the problem of long queries is not Access's problem, but the problem of the one who designed the database and wrote queries to it.
Refactor your work with the database and you will be happy.