||Re: complex indexes vs index key fields
Gaetano De Luisi <firstname.lastname@example.org>
||Tue, 28 Jul 2020 07:32:03 -0400
I opened and SET the database to the BDE alias I created, then USE the table and APPEND FROM the DBF file on my computer.
The 64-bit did not seem to work. It was unsuccessful until I deleted the ODBC DSN I had created with the 64-bit version. I don't have enough understanding of that to comment any further, all I can say is that the 32-bit version of the ODBC connector works.
I will look into ADO, I have never used it before.
Akshat Kapoor Wrote:
> On 28.07.2020 10:32, Gaetano De Luisi wrote:
> > It seems that 32-bit is the only one visible to the BDE administrator. Now I realise that those are drivers and the 32/64 bit versions are not interchangeable...
> > I have two choices still: ANSI or Unicode. For testing purposes I chose ANSI as I only need accented characters, not the whole range of encodeable characters, but I must say I don't fully understand the implications. The description of the database on the server says latin-swedish-case insensitive, so that seems to match the ANSI character set as far as my character set knowledge goes.
> > I tried ANSI and was able to set up the the ODBC alias and the BDE alias. After stumbling on a few hurdles, the following tutorial helped me create a table from dBase into the SQL database (http://www.dbasehost.com/tutorials/mysql1.php).
> > I then tried to append the data from my DBF file to the server but that is taking forever, about 350 records per minute... can I interrupt the append process without corrupting teh database? can you suggest a more efficient way to load data to the database server?
> Good Morning Gaetano,
> I prefer to install both 32 bit and 64 bit drivers.
> I have never required extended char set so never tried ansi or unicode.
> Just proceeded with the default whatever that is.
> If you access RDBMS through BDE then that defeats the purpose of using
> RDBMS. I would advise connecting using ADO.
> I have never used a dbase app with a website and hence cannot comment
> much on that.
> While uploading data interrupting should not corrupt a database. These
> are robust enough to withstand connection interruptions.
> How are you uploading data I have no idea hence cannot comment about
> alternative methods.
> Will this upload be a one time operation or a regular operation.
> I would suggest you harvest the power of full sql available with MySQL.
> Just google "sql insert multiple rows" and you will get a variety of
> Inserting 5 rows with a single sql will take approx the same time as
> inserting a single row.
> Have a look at these.