Pongracz Istvan

Great! Just curiosity: did you test it with the latest Postgresql (9.x and/or 10.x)? I guess, it should work without problem.

I reinstalled VFront, now the VFront tables are in the same Postgresql database as the DB itself. Now when I imported the DB into the frontend, the Compatibility test showed only 4 errors instead of 12 (no primary keys). So, in general, it seems using sqlite as vfront backend is not really a good idea. Note: I had to increase the size of commento (varchar 255) in all vfront tables, otherwise I was not able to import the DB. This is because I had heavy comments on the tables.

In other table VFront was able to see the Primary Key. The difference could be, the problematic table has foreign key, too. Here are the constraints: CONSTRAINT msz_id_pk PRIMARY KEY (id), CONSTRAINT fid_fk FOREIGN KEY (fid) REFERENCES mf (id) MATCH SIMPLE ON UPDATE NO ACTION ON DELETE NO ACTION

It seems VFront just cannot see the Primary Key of the table in Postgresql 8.4. There is a primary key defined in the table, but VFront cannot see it.

Some progress: VFront has log, where I can found some leads. It seems the missing Primary Key is the reason, why the grid view is empty, at least in my case. Here is the relevant part from the log: LINE 1: SELECT as pk, fsz,cd,vk,vn,vg,var... ^ SELECT as pk,

Hi, This bug still exists in 0.99.5. I have Database is on Postgresql 8.4 (yes, old), Vfront in sqlite Table in the database has no primary key. In the browser I cannot see any relevant issue (Shift+F8 devtools, console) What can I do solve this issue? What kind of info do you need to solve this? Thanks, István

1.4 Malay language support - some issues

github commits: 640 and 641