Daniel Kasak schrieb:
Andreas Moroder wrote:
Daniel Kasak schrieb:
You won't break anything by adding a timestamp field. Trust us :)
And no, there is no way around this problem other than adding a
timestamp field.
From the 'mysql' command-line client, do:
... where DATABASE_NAME is the nam
Andreas Moroder wrote:
> Daniel Kasak schrieb:
>> Andreas Moroder wrote:
>>
>>> Hello,
>>>
>>> when I open mysql table with access 97 using the latet mysql-odbc
>>> driver ( 3.51.12 ) I see only deleted records.
>>>
>>> What is happening ?
>>>
>>> I found many posts about this problem, but I can no
Daniel Kasak schrieb:
Andreas Moroder wrote:
Hello,
when I open mysql table with access 97 using the latet mysql-odbc
driver ( 3.51.12 ) I see only deleted records.
What is happening ?
I found many posts about this problem, but I can not, as told in this
posts, add timestamp or other fields
Andreas Moroder wrote:
> Hello,
>
> when I open mysql table with access 97 using the latet mysql-odbc
> driver ( 3.51.12 ) I see only deleted records.
>
> What is happening ?
>
> I found many posts about this problem, but I can not, as told in this
> posts, add timestamp or other fields because thi
I see. I added the timestamp field (I never knew there was a field type
of timestamp), relinked the table in Access 2000 and the darn thing
actually worked! Did this just become a requirement in MySQL 3.23? As I
mentioned in a previous post, the timestamp field was not required when I
was w
suppose if it still doesn't work right, I will just have to install
some 3.22 version of MySQL.
Christopher Lewis
>>>>>>>>>>>>>>>>>> Original Message <<<<<<<<<<<<<<<<<<
On 3/14/01, 10:
Hello Christopher,
CL> Is anybody aware of a problem when connecting Microsoft Access to MySQL
CL> 3.23 where records with AutoIncrement fields claim to be deleted after
CL> entry? Here's what I have:
Yep!
[...]
CL> autoincrement field, it will not have this problem. Is there anything I
CL
