Restored from previous forum. Originally posted by Saboteur.
@El_Choni
UPDATE: added SQLiteField() for 1.33. If you need it now, e-mail me and I'll send you the lib (beta).
Yaaa?? Already? In 2 hours? You are the Master...
@Manolo
I think that not is one good idea Choni, because this is very easy with sql directly, for example:
SELECT Clave, Nombre,Privilegio FROM identity WHERE Clave LIKE '"+MyPassword'
And not is neccesary call to function. If Result=OK you only need this code:
cadena=SQLiteData(1,1)or 1,2, etc without for, next and other "pamplinas"
Remember the last month and problems unnecesaries to build new functions for this. SQL solve the problem. And the old math is solve with easy SELECT's in SQL.
Yes, it is possible, but...
1. if you have a table with n fields, is more readable
----select * from table; than
----select field1, field2, field3 .... fieldN from table
2. in the code, is more readable too, and this is the first problem i've found. I don't remember the fields position, and need the database script.
----SQLiteField(1,"name"); than
----SQLiteData(1,3)
3. if you insert a field in a large table, well "select * from ...", you'll have to let the field at last position to avoid problems with writed code.
Anyways, I'm using that function already, it was a sugestion.
Win98 Athlon 1200 256DDR ATI RADEON 9000