Results for "Author: williams castillo"
The purpouse of this module is to backup and restore mysql databases within a Visual Basic program. Please, don't vote for this one... It is a remake of http://www.planetsourcecode.com/vb/scripts/ShowCode.asp?txtCodeId=57138&lngWId=1 which inspires me. It has some improvement on his code: Basically, it take the table creation statement directly from the MySQL engine (so now it publish constrains and indexes correctly) and perfom only on insertion statement per table no matter the number of rows in the table. Also, it prevent MySQL from generating errors because of the constraing and block the tables before the insertion process. Also, it could allows the programmers to give feedback to the user about the process and, last but not least, it is IMHO a bit cleaner.
The purpouse of this module is to backup and restore mysql databases within a Visual Basic program. Please, don't vote for this one... It is a remake of http://www.planetsourcecode.com/vb/scripts/ShowCode.asp?txtCodeId=57138&lngWId=1 which inspires me. It has some improvement on his code: Basically, it take the table creation statement directly from the MySQL engine (so now it publish constrains and indexes correctly) and perfom only on insertion statement per table no matter the number of rows in the table. Also, it prevent MySQL from generating errors because of the constraing and block the tables before the insertion process. Also, it could allows the programmers to give feedback to the user about the process and, last but not least, it is IMHO a bit cleaner.
The purpouse of this module is to backup and restore mysql databases within a Visual Basic program. Please, don't vote for this one... It is a remake of http://www.planetsourcecode.com/vb/scripts/ShowCode.asp?txtCodeId=57138&lngWId=1 which inspires me. It has some improvement on his code: Basically, it take the table creation statement directly from the MySQL engine (so now it publish constrains and indexes correctly) and perfom only on insertion statement per table no matter the number of rows in the table. Also, it prevent MySQL from generating errors because of the constraing and block the tables before the insertion process. Also, it could allows the programmers to give feedback to the user about the process and, last but not least, it is IMHO a bit cleaner.
The purpouse of this module is to backup and restore mysql databases within a Visual Basic program. Please, don't vote for this one... It is a remake of http://www.planetsourcecode.com/vb/scripts/ShowCode.asp?txtCodeId=57138&lngWId=1 which inspires me. It has some improvement on his code: Basically, it take the table creation statement directly from the MySQL engine (so now it publish constrains and indexes correctly) and perfom only on insertion statement per table no matter the number of rows in the table. Also, it prevent MySQL from generating errors because of the constraing and block the tables before the insertion process. Also, it could allows the programmers to give feedback to the user about the process and, last but not least, it is IMHO a bit cleaner.
The purpouse of this module is to backup and restore mysql databases within a Visual Basic program. Please, don't vote for this one... It is a remake of http://www.planetsourcecode.com/vb/scripts/ShowCode.asp?txtCodeId=57138&lngWId=1 which inspires me. It has some improvement on his code: Basically, it take the table creation statement directly from the MySQL engine (so now it publish constrains and indexes correctly) and perfom only on insertion statement per table no matter the number of rows in the table. Also, it prevent MySQL from generating errors because of the constraing and block the tables before the insertion process. Also, it could allows the programmers to give feedback to the user about the process and, last but not least, it is IMHO a bit cleaner.
The purpouse of this module is to backup and restore mysql databases within a Visual Basic program. Please, don't vote for this one... It is a remake of http://www.planetsourcecode.com/vb/scripts/ShowCode.asp?txtCodeId=57138&lngWId=1 which inspires me. It has some improvement on his code: Basically, it take the table creation statement directly from the MySQL engine (so now it publish constrains and indexes correctly) and perfom only on insertion statement per table no matter the number of rows in the table. Also, it prevent MySQL from generating errors because of the constraing and block the tables before the insertion process. Also, it could allows the programmers to give feedback to the user about the process and, last but not least, it is IMHO a bit cleaner.
The purpouse of this module is to backup and restore mysql databases within a Visual Basic program. Please, don't vote for this one... It is a remake of http://www.planetsourcecode.com/vb/scripts/ShowCode.asp?txtCodeId=57138&lngWId=1 which inspires me. It has some improvement on his code: Basically, it take the table creation statement directly from the MySQL engine (so now it publish constrains and indexes correctly) and perfom only on insertion statement per table no matter the number of rows in the table. Also, it prevent MySQL from generating errors because of the constraing and block the tables before the insertion process. Also, it could allows the programmers to give feedback to the user about the process and, last but not least, it is IMHO a bit cleaner.
The purpouse of this module is to backup and restore mysql databases within a Visual Basic program. Please, don't vote for this one... It is a remake of http://www.planetsourcecode.com/vb/scripts/ShowCode.asp?txtCodeId=57138&lngWId=1 which inspires me. It has some improvement on his code: Basically, it take the table creation statement directly from the MySQL engine (so now it publish constrains and indexes correctly) and perfom only on insertion statement per table no matter the number of rows in the table. Also, it prevent MySQL from generating errors because of the constraing and block the tables before the insertion process. Also, it could allows the programmers to give feedback to the user about the process and, last but not least, it is IMHO a bit cleaner.
The purpouse of this module is to backup and restore mysql databases within a Visual Basic program. Please, don't vote for this one... It is a remake of http://www.planetsourcecode.com/vb/scripts/ShowCode.asp?txtCodeId=57138&lngWId=1 which inspires me. It has some improvement on his code: Basically, it take the table creation statement directly from the MySQL engine (so now it publish constrains and indexes correctly) and perfom only on insertion statement per table no matter the number of rows in the table. Also, it prevent MySQL from generating errors because of the constraing and block the tables before the insertion process. Also, it could allows the programmers to give feedback to the user about the process and, last but not least, it is IMHO a bit cleaner.
The purpouse of this module is to backup and restore mysql databases within a Visual Basic program. Please, don't vote for this one... It is a remake of http://www.planetsourcecode.com/vb/scripts/ShowCode.asp?txtCodeId=57138&lngWId=1 which inspires me. It has some improvement on his code: Basically, it take the table creation statement directly from the MySQL engine (so now it publish constrains and indexes correctly) and perfom only on insertion statement per table no matter the number of rows in the table. Also, it prevent MySQL from generating errors because of the constraing and block the tables before the insertion process. Also, it could allows the programmers to give feedback to the user about the process and, last but not least, it is IMHO a bit cleaner.