Activity for Marciel Degasperi
-
Marciel Degasperi committed [94bedd] on Code
Small bugfixes.
-
How to add BMP image in OLE field
-
Hi, Thanks for reporting. Unfortunately, there is currently no way to upload an image with MDB Admin. There is very few documentation about the OLE format, so I haven't found ways to create the necessary file headers. Either way, I'll keep this ticket open and do further research at this point.
-
DBPROP_JETOLEDB_COL_COMPRESSED not set w Add Column
-
I tried several ways, but each time an error occurred when trying to change this property via ADOX. I think it's a bug in this library, but the equivalent property ("Jet OLEDB:Compressed UNICODE Strings") cannot be set. The only way to add a command to configure this option would be to use some resource external to ADOX, such as an SQL command. However, this adds a layer of complexity to the application, which I intend to avoid until more similar functionality is needed. Alternatively, you have a...
-
conversione mdb
-
Grazie per la segnalazione. Per effettuare la conversione è necessario installare il "Microsoft Access Database Engine Redistributable 32bits". Puoi ottenerlo dalla pagina ufficiale di Microsoft o dai collegamenti disponibili con il progetto.
-
Microsoft Access Database Engine Redistributable 32-bit is no longer available
-
Thanks for reporting. You can use the 2016 version without any problems. Enter the link below and select the 32-bit version when prompted: https://www.microsoft.com/EN-US/DOWNLOAD/confirmation.aspx?id=54920 I will update the main link.
-
-
New option "Copy All" in properties window.
-
Ok, I got it. I'm going to do some tests, but I believe it is not possible to change this property, as well as others properties. MDB Admin uses ADOX, and this has some limitations. If it is possible, I will add the option to the columns "Edit" menu. Meanwhile, you can create columns with the instruction below: ALTER Table Movies ADD Column COUNTRY3 TEXT(60) WITH COMPRESSION
-
DBPROP_JETOLEDB_COL_COMPRESSED not set w Add Column
-
DBPROP_JETOLEDB_COL_COMPRESSED not set w Add Column
-
Thanks for reporting. I am unable to reproduce the problem. In my tests, columns created by the table creation wizard or the column creation wizard were generated with the mentioned option. Please detail step by step how you encountered the problem. If possible, send a database file with a test case.
-
DBPROP_JETOLEDB_COL_COMPRESSED not set w Add Column
-
Add inno setup config files.
-
Minor fixes in translation
-
Can't save
-
Corrections and optimization when exporting tables.
-
I got it. You are using "View/Edit Data" option to create the SQL code. Using this option, you cannot change or save the generated SQL, as this is a feature designed only to view table data. You can use the "Template"->"SELECT" option to create a basic SQL from the table, which can be edited and saved as needed. You can also drag the table to the editing area, and a menu with templates will be displayed. Note that the Save option saves the SQL code as a file. To save edits to the table data, use...
-
I got it. You are using "View/Edit Data" option to create the SQL code. Using this option, you cannot change or save the generated SQL, as this is a feature designed only to view table data. You can use the "Template"->"SELECT" option to create a basic SQL from the table, which can be edited and saved as needed. You can also drag the table to the editing area, and a menu with templates will be displayed.
-
I got it. You are using "View/Edit Data" option to create the SQL code. Using this option, you cannot change or save the generated SQL, as this is a feature designed only to view table data. You can use the "Template"->"SELECT" option to create a basic SQL from the table, which can be edited and saved as needed.
-
Can't save
-
Thanks for reporting. Could you please send a screenshot of this problem? In my tests I was unable to reproduce what you reported. See image below. However, I identified another issue when saving edited SQL files, which was fixed in version 2.5.11.830.
-
Fixed issue when saving edited SQL files;
-
Error: Syntax error in FROM clause
-
Thanks for reporting. Fixed in version 3.5.10.823.
-
Error: Invalid file "المحاسب الذكي.lnk".
-
Thanks for reporting. Fixed in version 3.5.10.823.
-
Ticket #127: Syntax error duplicating a table with special chars in name;
-
Error: Invalid file "المحاسب الذكي.lnk".
-
Error: 无效的 SQL语句；期待 'DELETE'、'INSERT'、'PROCEDURE'、'SELECT'、或 'UPDATE'。
-
Thanks for reporting. I tested your SQL and it worked as expected. I think you selected a part from the query when executing, this instructs MDB Admin to only execute the selected text, which may have caused the problem. See the images for more details.
-
Thanks for reporting. I tested your SQL and it worked as expected. I think you selected an excerpt from the query when executing, this instructs MDB Admin to only execute the selected text, which may have caused the problem. See the images for more details.
-
Hi, thanks for reporting. The terms “user” and “password” are reserved words in SQL. To use them as column names, you need to add square brackets to them. See the example below: INSERT INTO [User](id, username, [password]) VALUES ('0001','zhangsan','123456'); INSERT INTO [User](id, username, [password]) VALUES ('0002','lisi','12345'); INSERT INTO [User](id, username, [password]) VALUES ('0003','wangwu','1234'); It is not recommended to use reserved words as database element identifiers. Try choosing...
-
Error: INSERT INTO 语句的语法错误。
-
How to convert .mdb file to .accdb
-
Hi, thanks for reporting. Please check if you followed all the steps: 1- Close MDB Admin, if it is running. 2- Install "Microsoft Access Database Engine Redistributable" 32bits. MDB Admin is a 32bit application, so the 64bit version of the engine will not work. 3- Open MDB Admin. You can check whether you have installed the correct version of the engine via MDB Admin, in the "Help" -> "About" menu. 4- Open you MDB file. 5- Access the menu "Database"->"Tools"->"Convert MDB <-> ACCDB". If it still...
-
Error: 在 SQL 语句结尾之后找到字符。
-
Hello, according to Google Translator you are executing SQL with an invalid character at the end of the statement. Please review your SQL and try again.
-
Error: Out of memory
-
Hello, thanks for reporting. I made a fix to optimize memory usage, and I hope it solves the problem you encountered. Please update MDB Admin to the latest version (2.5.9). I successfully tested these settings in a virtual machine with 1.5GB RAM exporting a 750MB database. Please let me know if the issue persists for you.
-
Ticket #121: Dump memory utilization optimized (again).
-
Error: Spreadsheet is full
-
Hi, Thanks for reporting. If you export a MDB file to Excel, it generate a XLS spreadsheet. XLS spreadsheets supports only 65536 rows. You can try converter MDB to ACCB and after export to excel. This way the output file will be XLSX, which supports up to 1048576 lines. But if your table has more than 1048576 rows, you need choose another output format.
-
Error: Out of memory
-
Hi, I can't open your file because it is password protected. This error can occur if the file is already opened by Access or another editor. Try closing other apps and try again. Best regards,
-
Error: The process cannot access the file because it is being used by another process
-
Hey, I can't open your file because it is password protected. This error can occur if the file is already opened by Access or another editor. Try closing other apps and try again. Best regards,
-
Hi Ron, Thanks for the suggestion. Your request has been implemented in version 2.5.8. Best regards.
-
Enhancement to PostgreSQL dump facility
-
Hi Ron, Thanks for the suggestion. Your request has been implemented in version 2.5.8. Best regards.
-
Enhancement to PostgreSQL dump facility
-
Add "Add quotes to all names" in Dump Options window (ticket #120);
-
Error: Syntax error in INSERT INTO statement
-
Closed due lack of information
-
Small bugfixes
-
Hi, Can you send me your SQL?
-
Error: Dépassement d'un champ numérique
-
Hi, you are probably inserting a numerical value greater than the defined value for the column. Check the data type of your table columns.
-
Error: Out of memory
-
Closed due to lack of information
-
Error: Not enough space on temporary disk
-
Edit table
-
It will be implemented on ticket #21
-
Olá Marinaldo, tudo bem? Obrigado pelo feedback. Por favor, envie mais detalhes sobre as operações nas quais encontrou lentidão que verificarei o que pode ser feito.
-
Closed due lack of information. Its appear be a SO problema.
-
Please send more details about this error.
-
Hi Martin, you need install "Microsoft Access Database Engine Redistributable" 32bits, which can be found at the link below: https://www.microsoft.com/en-us/download/details.aspx?id=13255 This engine is required to work with new Access database format.
-
Fixed in version 2.5.6.798
-
Error: Out of memory
-
Fixed in version 2.5.6.799
-
Ticket #111: Dump memory utilization optimized.
-
Error: Out of memory
-
New language pack
-
Small bugfixes in template queries generation.
-
Error: Out of memory
-
Closed due lack of information.
-
Error: Cannot create file "C:\Program Files (x86)\AthenaCentral\AthenaCentral2020\athenatest.sql". Access is denied
-
This is not an MDB Admin problem. Apparently, your Windows user does not have permission to edit or save files in the path "C:\Program Files (x86)\AthenaCentral\AthenaCentral2020\".
-
Error: Cannot create file "C:\Program Files (x86)\AthenaCentral\AthenaCentral2020\athenatest.sql". Access is denied
-
This is not an MDB Admin problem. Apparently, your Windows user does not have permission to edit or save files in the path "C:\Program Files (x86)\AthenaCentral\AthenaCentral2020\".
-
Error: Record(s) cannot be deleted; no delete permission on 'MyInformation'
-
Closed due lack of information.
-
Error: Record(s) cannot be read; no read permission on 'MyInformation1'
-
Closed due lack of information.
-
Error: Out of memory
-
Thanks for reporting. Can you send me your database file?
-
Add "Serializable" to classes to avoid "NotSerializableException" in Jasper
-
It looks like your database is corrupted. Can you send the mdb file for me to check?
-
It looks like your database is corrupted. Can you send the mdb file for me to check?
-
SQL dump for SQLite uses wrong representation of Infinity and NaN
-
Fix in version 2.5.4. Since there is no representation for NaN and Infinity in SQL, I had these values converted to NULL, with a little comment showing the original value. Thanks for reporting.
-
Fix ticket #105.
-
Error: Invalid class string, ProgID: "DAO.DBEngine.120"
-
Please install "Microsoft Access Database Engine Redistributable" 32bits, which can be found at the link below: https://www.microsoft.com/en-us/download/details.aspx?id=13255
-
SQL dump for SQLite uses wrong representation of Infinity and NaN
-
I haven't found a way to insert NaN or infinity into an Access database. Can you send me your database with these conditions?
-
SQL dump should be in UTF-8, in order to support accented characters
1 >