Re: Access XP crashes regularly when linked to MySQL via MyODBC

2003-01-30 Thread Daniel Kasak
Loren McDonald wrote:


Have you done all the office (or at least Access) XP updates?  If not,
it is possible that one of them my resolve your crash problem.  I have
been testing Access XP with the same versions of MyODBC and MySQL for a
few weeks now and have yet to see a crash.  About the only problem I
have ran into is MySQL shutting down, for no apparent reason, every so
often.  I have just installed .55, so I'm waiting to see if it is still
a problem.
 

Can't speak for others, but...
I've got the latest MDAC (2.7).
I have tested with Access XP - bare, Service Pack 1 and Service Pack 2.
I have also tried with a few startup switches, eg /safe which was 
recommended to me by M$ helpdesk.
MyODBC options:

- Don't Optimize Column Width
- Return Matching Rows
- Change BIGINT Columns to INT

Drifting off topic...

Also, not only does the developer version of Access crash, but the 
deployable, cut-down versions you can make with the packaging wizard 
also crash similarly.
One stange thing I've noticed is that whereas sometimes Access will 
crash outright, other times it will simply prevent you from exiting the 
current record. If you try to either:

- exit the form, or
- move the focus to a sub / parent form, or
- move to another record,

Access will give an error dialog saying that the current action will 
halt any running code, even though there is no code running. Pressing 
either the 'End' or 'Debug' buttons results in the same dialog box 
re-appearing (in modal form). The only thing you can do at this point is 
to use the task manager to shut down Access.

Also, (nearly finished) the deployable cut-down version, which isn't 
supposed to have any form / code editing abilities, also gives the 'End' 
/ 'Debug' dialog.

The above problem is another reason why I think the bug is in Access.

--
Daniel Kasak
IT Developer
* NUS Consulting Group*
Level 18, 168 Walker Street
North Sydney, NSW, Australia 2060
T: (+61) 2 9922-7676 / F: (+61) 2 9922 7989
email: [EMAIL PROTECTED]
website: www.nusconsulting.com


-
Before posting, please check:
  http://www.mysql.com/manual.php   (the manual)
  http://lists.mysql.com/   (the list archive)

To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php



RE: Access XP crashes regularly when linked to MySQL via MyODBC

2003-01-28 Thread Loren McDonald
Have you done all the office (or at least Access) XP updates?  If not,
it is possible that one of them my resolve your crash problem.  I have
been testing Access XP with the same versions of MyODBC and MySQL for a
few weeks now and have yet to see a crash.  About the only problem I
have ran into is MySQL shutting down, for no apparent reason, every so
often.  I have just installed .55, so I'm waiting to see if it is still
a problem.

-- 
Loren McDonald
[EMAIL PROTECTED]

> -Original Message-
> From: M Wells [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, January 28, 2003 10:19 AM
> To: [EMAIL PROTECTED]
> Subject: Access XP crashes regularly when linked to MySQL via MyODBC
> 
> Hi All,
> 
> My MySQL Server is 3.23.53-max-nt. I'm linking to it via MyODBC
> 3.51.05.00 and accessing its tables via Access XP linked tables.
> 
> For some reason, Access XP crashes regularly in this setup. No
> meaningful error messages, just crashes and reloads after a repair.
Even
> more odd (and I only have subjective observation to back this up), it
> appears to only crash when left unattended for a period of time.
> Although, maybe I have that impression because when left alone for a
> period of time equates to running long enough to have encountered a
> problem?
> 
> Is this a known problem with MySQL 3.23.53-max-nt / MyODBC 3.51.05.00
/
> Access XP?
> 
> Regards and best wishes,
> 
> Murray Wells
> 
> 
> 
> -
> Before posting, please check:
>http://www.mysql.com/manual.php   (the manual)
>http://lists.mysql.com/   (the list archive)
> 
> To request this thread, e-mail <[EMAIL PROTECTED]>
> To unsubscribe, e-mail  [EMAIL PROTECTED]>
> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php





-
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/   (the list archive)

To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php




Re: Access XP crashes regularly when linked to MySQL via MyODBC

2003-01-28 Thread Daniel Kasak
M Wells wrote:


Hi All,

My MySQL Server is 3.23.53-max-nt. I'm linking to it via MyODBC
3.51.05.00 and accessing its tables via Access XP linked tables.

For some reason, Access XP crashes regularly in this setup. No
meaningful error messages, just crashes and reloads after a repair. Even
more odd (and I only have subjective observation to back this up), it
appears to only crash when left unattended for a period of time.
Although, maybe I have that impression because when left alone for a
period of time equates to running long enough to have encountered a
problem? 

Is this a known problem with MySQL 3.23.53-max-nt / MyODBC 3.51.05.00 /
Access XP?
 

Yeah I can confirm this problem.
We use MySQL-4.0.x and MyODBC-3.51.x - whatever's the latest.
I have had a few discussions in the MyODBC mailing list about it.
It seems to be a problem with Access XP.
I also noticed that it seems to happen when Access is left inactive for 
5 minutes or more.
This lead me to believe that MySQL is closing the client connection 
after a period of time and Access isn't handling it very gracefully. 
However the period of time isn't fixed, and sometimes it can stay open 
for an hour without crashing. I don't know what's up, but I'm sure it's 
Access' fault. The crash I get is one of those hardcore "Microsoft 
appologises for the inconvenience. Would you like to send a bug report. 
Yes / No" ones. They know they are to blame...

I've called M$ tech support about it, and they only want to hear about 
it after I give them $AUS290. Since it's not really a show-stopper for 
us - just bloody annoying - I've left it at that. They (M$) say they 
will refund the $290 if they find that the problem is actually a bug in 
their software. But I don't really trust them on that. I'd rather give 
the money to TheKompany for a product like 
http://www.thekompany.com/products/rekall/ which is like Access only I 
assume it doesn't crash so much, and it uses Python instead of visual 
basic. It's not particularly advanced yet, but as I said, I'd rather 
give money to them to improve their product than give it to M$ so they 
can rehash the same trash (and add a few bugs while they're at it) every 
18 months.

One dodgy workaround I've considered is to have a hidden form in Access 
that opens when the database opens. Put a timer event on it to run the 
OnTimer() code every 5 minutes or so. And the code just refreshes the 
form which is linked to a dummy table in MySQL. I haven't tried this 
myself but I have a feeling it will work.

Tell me how you get on anyway. It you need an Australian to back up your 
crash reports I'm more than willing to add my name to the complaints 
list yet again ;-)

--
Daniel Kasak
IT Developer
* NUS Consulting Group*
Level 18, 168 Walker Street
North Sydney, NSW, Australia 2060
T: (+61) 2 9922-7676 / F: (+61) 2 9922 7989
email: [EMAIL PROTECTED]
website: www.nusconsulting.com


-
Before posting, please check:
  http://www.mysql.com/manual.php   (the manual)
  http://lists.mysql.com/   (the list archive)

To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php



RE: Access XP crashes regularly when linked to MySQL via MyODBC

2003-01-28 Thread Victor Pendleton
I have seen this behavior reported several times in regards to the MySQL
being accessed via MyODBC and MS Access, (various versions). Are you
detailing that Access crashes and you have to repair the MySQL tables? If
so, is there an error being written to the MySQL error log?

-Original Message-
From: M Wells [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, January 28, 2003 9:19 AM
To: [EMAIL PROTECTED]
Subject: Access XP crashes regularly when linked to MySQL via MyODBC


Hi All,

My MySQL Server is 3.23.53-max-nt. I'm linking to it via MyODBC
3.51.05.00 and accessing its tables via Access XP linked tables.

For some reason, Access XP crashes regularly in this setup. No
meaningful error messages, just crashes and reloads after a repair. Even
more odd (and I only have subjective observation to back this up), it
appears to only crash when left unattended for a period of time.
Although, maybe I have that impression because when left alone for a
period of time equates to running long enough to have encountered a
problem? 

Is this a known problem with MySQL 3.23.53-max-nt / MyODBC 3.51.05.00 /
Access XP?

Regards and best wishes,

Murray Wells



-
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/   (the list archive)

To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail
<[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php

-
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/   (the list archive)

To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php




Access XP crashes regularly when linked to MySQL via MyODBC

2003-01-28 Thread M Wells
Hi All,

My MySQL Server is 3.23.53-max-nt. I'm linking to it via MyODBC
3.51.05.00 and accessing its tables via Access XP linked tables.

For some reason, Access XP crashes regularly in this setup. No
meaningful error messages, just crashes and reloads after a repair. Even
more odd (and I only have subjective observation to back this up), it
appears to only crash when left unattended for a period of time.
Although, maybe I have that impression because when left alone for a
period of time equates to running long enough to have encountered a
problem? 

Is this a known problem with MySQL 3.23.53-max-nt / MyODBC 3.51.05.00 /
Access XP?

Regards and best wishes,

Murray Wells



-
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/   (the list archive)

To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php