ok thx you VM i'm waiting for it :)Quote:
ya indeed 1433 not 1443. You can use [Only registered and activated users can see links. Click Here To Register...] to post images
For how to add a data source, i will add a mini tutorial
ok thx you VM i'm waiting for it :)Quote:
ya indeed 1433 not 1443. You can use [Only registered and activated users can see links. Click Here To Register...] to post images
For how to add a data source, i will add a mini tutorial
You need to put SQL as data source, as the text select in your screen.Quote:
Sorry glandu2 but i still can't connet to my database :( i tryed to mace ODBC conection but it couldn't helt... I make sql conection with 1334 port; the rest configuration is in this img. :) Help me plz if u can :) Thx you a lot!
Thx u VM :) Now all work ur my superman :D Ty againQuote:
I am trying to support nvarchar, that is unicode characters, but the RDB file is using non unicode data (which is why there are many ??? in db_string.rdb), and unicode things are used differently on windows than on linux, so you can have broken characters when dealing with non native characters from the SQL table or the RDB.
Any way, here are the screen of how I add a data source (I did not change anything not shown in these screens) :
Working on that ^^ ATM I can import the arabic stringresource from the DB on my computer which use franch characters, and it works on linux. I have some issue with iconv on windows, but I just found a way to bundle it within my tool (so no additionnal libiconv.dll)Quote:
does your tool import non english chars? cause i tried to import koréan string resource but that didn't work very well
this tool is more than any noob like me ever used, so any way wont make this tool worse=) btw idk how anyone thinks about it but i think if you will add a hasher in additional window (combobox where user can chose one of default rdb names or type own and textbox where hashed file name will be shown) with correct hasher for any filename, even not included in client as default, it will be the greatestQuote:
Indeed, but which way would be better to add that feature ?
I think of a checkbox, that tell when opening/saving a RDB file to either use the default filename or the hashed default filename as the default name in the file dialogbox
So with that, I will add default RDB filename and default SQL table name (CSV filename would be the rdb one but with csv extension)
Yes, I pretty much worked that out. This works when you are reading from a rdb and saving into sql. That's wasn't my problem. My problem is when loading from sql then saving to rdb, it doesn't works like intended.Quote:
{MAKEINDEXEDVAR(2, 1), TYPE_DECIMAL, "delay_cast"}
indicate that the value is a decimal number stored as an integer with two digits after the comma.
So: the integer 500 in the RDB will be read as 5.00, 1203 would be read as 12.03
So if there is only one digit after the comma, replace the 2 with 1.
If you need to put a 0 instead of the 2, just make it a TYPE_INT32:
{1, TYPE_INT32, "delay_cast"}
Because a decimal with 0 digit after the comma is just a int32
Weird, I don't have this crash, but found a crash when loading SQL table with 0 length stringsQuote:
Testing the updated version. I believe the save rdb button is broken. I load from sql then hit save to rdb, it auto names it db_skill.rdb but then I hit save, the program crashes (standard Windows crash report error dialog).
Looks like type_decimal is fixed, as when I load from sql, delay cast values looks fine. But cannot really test to see since I cannot save into rdb and run test server/client. XD