Kérlek a kód tagokat a megfelelő rendeltetésük szerint használd.
 

Nem értem a problémád.
 
[/quote]
Szerkesztettem neked, most nézd meg. És szűrd le a kettő közti különbséget.

[code][ /code]

Ezen a 2. code snippeteden beszartam, erre fogadni mernek, hogy nem mukodik.
De gondolom mivel 0-rol irt, tudod hol a hiba
 

 

Rövidre zárva: Ha legközelebb is elmarad a kód használat, akkor figyelmeztetésben részesülsz. Most megúsztad egy írásbeli figyúval.
 
[/quote]
Akkor kérlek írd le a kódsor pontos használatát. Mert nem rendeltetés szerűen működik, hanem kitalált rendszer alapján.
 
[/quote]
Tudom miről beszélsz. De akkor az infókat is illesszem a kódba?

    local adatok = {
    [\"hoszt\"] = \"\",
    [\"jelszo\"] = \"\",
    [\"felhasznalo\"] = \"\",
    [\"adatbazisNev\"] = \"\",
    }
     
     
    function csatlakozasAdatbazishoz()
            csatlakozas = dbConnect(\"mysql\",\"adatbazisNev=\".. lekerdezTombAlapjan()[\"adatbazisNev\"] ..\";hoszt=\"..lekerdezTombAlapjan()[\"hoszt\"], lekerdezTombAlapjan()[\"felhasznalo\"], lekerdezTombAlapjan()[\"jelszo\"], \"megosztas=1\")
            if csatlakozas then
                    outputDebugString(\"Mysql-re sikeresen csatlakoztam.\")
            else
                    outputDebugString(\"A csatlakozás a mysql-re sikertelen.\")
                    cancelEvent(true)
            end
    end
    addEventHandler(\"onResourceStart\", getRootElement(), csatlakozasAdatbazishoz)
     
    function lekerdezCsatlakozas()
            return csatlakozas
    end
     
    function lekerdezTombAlapjan()
            return adatok
    end

    databaseType: The type of database. This can be either sqlite or mysql
    host: The target to connect to. The format of this depends on the database type.
        For SQLite it is a filepath to a SQLite database file. If the filepath starts with \":/\" then the server\'s global databases directory is used. The file will be created if it does not exist.
        For MySQL it is a list of key=value pairs separated by semicolons. Supported keys are:
            dbname: Name of the database to use e.g. dbname=test
            host: Host address e.g. host=127.0.0.1
            port: Host port e.g. port=1234 (optional, defaults to standard MySQL port if not used)
            unix_socket: Unix socket or named pipe to use (optional)
            charset: Communicate with the server using a character which is different from the default e.g. charset=utf8 (optional)
 
    username: Usually required for MySQL, ignored by SQLite
    password: Usually required for MySQL, ignored by SQLite
    options : List of key=value pairs separated by semicolons. Supported keys are:
        share which can be set to 0 or 1. (Default value for SQLite is \"share=1\", for MySQL is \"share=0\"). When set to 1, the connection is shared and will be used by other calls to dbConnect with the same host string. This is usually a good thing for SQLite connections, but not so good for MySQL unless care is taken.
        batch which can be set to 0 or 1. (Default is \"batch=1\"). When set to 1, queries called in the same frame are automatically batched together which can significantly speed up inserts/updates. The downside is you lose control of the feature that is used to achieve batching (For SQLite it is transactions, for MySQL it is autocommit mode). Therefore, if you use transactions, lock tables or control autocommit yourself, you may want to disable this feature.
        autoreconnect which can be set to 0 or 1. (Default value \"autoreconnect=1\"). When set to 1, dropped connections will automatically be reconnected. Note that session variables, user variables, table locks and temporary tables will be reset because of the reconnection. So if you use these fancy features, you will need to turn autoreconnect off and cope with dropped connections some other way.
        log which can be set to 0 or 1. (Default value \"log=1\"). When set to 0, activity from this connection will not be recorded in the database debug log file.
        tag (Default value \"tag=script\"). A string which helps identify activity from this connection in the database debug log file.
        suppress A comma separated list of error codes to ignore. (eg. \"suppress=1062,1169\").
FROM VERSION 1.5.2 r7972 ONWARDS
        multi_statements Enable multiple statements (separated by a semi-colon) in one query. Use dbPrepareString when building a multiple statement query to reduce SQL injection risks.