------------=_1106173329-28169-4
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Hi all.

I've been testing MyODBC-3.51.10 on my PC and a handful of other PCs (
all Win2k sp4 ) for a couple of days now with no issues.
I've been using Access XP ( developer ) on my PC, and the 'runtime'
version of Access XP ( that the developer version creates ) on other PCs.

So I decided to go around last night and upgrade all PCs. Bad idea ...

Basically all of the PCs I upgraded refuse to talk to MySQL ( which I
only discovered this morning ). I can make a connection in the ODBC
administrator thing - it connects fine ( we are using System DSNs, by
the way ). But if I launch MS Access and open a form that connects to
MySQL, I get the error: 'execution of this application has produced a
runtime error' and Access closes. Unfortunately, the 'runtime' version
of Access doesn't allow you to open tables directly, or inspect any
code-generated errors - it simply closes itself at the first sign of
trouble. I can't reproduce the error on my system.

Installation procedure:

- log in as administrator
- remove MyODBC via add / remove wizard
- open windows explorer, select the 'winnt' folder, right-click,
'search' for myodbc and delete all files found
- click on downloaded MyODBC MSI installer
- test connection in ODBC administrator

I've repeated this process a number of times on my PC and on some of the
'problem' PCs. I can't get the problem ones to work, and I can't get
mine to give a problem.

Some of the other testing PCs ( that worked fine, hence the site-wide
upgrade ) are set up *identically* to the problem PCs - runtime version
of Access, same NT domain security settings, etc. Admittedly the MS
Access front-ends were different, but I don't see how that would give
any issues - all the front-ends work in the same way ... mostly simple
forms with linked tables.

I have also tried both versions of MyODBC-3.51.10 - the original and the
-2 version. Same problem.

If I *must*, I can try to assemble a small test case that causes the
problem. I've obviously moved everyone back to MyODBC-3.51.9 now ( a
lengthy process ), and I don't have any spare PCs, so further testing is
going to be an out-of-hours job.

Let the lone system administrator beware :)

--
Daniel Kasak
IT Developer
NUS Consulting Group
Level 5, 77 Pacific Highway
North Sydney, NSW, Australia 2060
T: (+61) 2 9922-7676 / F: (+61) 2 9922 7989
email: dkasak [at] nusconsulting.com.au
website: http://www.nusconsulting.com.au


------------=_1106173329-28169-4
Content-Type: text/plain; charset=us-ascii

--
MySQL ODBC Mailing List
For list archives: http://lists.mysql.com/myodbc
To unsubscribe: http://lists.mysql.com/myodbc?unsub=gcdmo-myodbc [at] m.gmane.org
------------=_1106173329-28169-4--

Daniel,

I have the similar setup , only my development machine is Windows XP.

Every morning in order to use MS-Access connected to MySQL, after MS-Access
was close previous evening, I have to refresh all linked tables using
"Linked tables manager".

It seems to me that in your runtime versions of the application you might
need to code abilitiy to resfresh all linked tables before use.

Regards,

Mikhail

----- Original Message -----
From: "Daniel Kasak" <dkasak [at] nusconsulting.com.au>
To: <myodbc [at] lists.mysql.com>
Sent: Wednesday, January 19, 2005 5:22 PM
Subject: MyODBC-3.51.10 ( both versions ) connection failure


> Hi all.
>
> I've been testing MyODBC-3.51.10 on my PC and a handful of other PCs (
> all Win2k sp4 ) for a couple of days now with no issues.
> I've been using Access XP ( developer ) on my PC, and the 'runtime'
> version of Access XP ( that the developer version creates ) on other PCs.
>
> So I decided to go around last night and upgrade all PCs. Bad idea ...
>
> Basically all of the PCs I upgraded refuse to talk to MySQL ( which I
> only discovered this morning ). I can make a connection in the ODBC
> administrator thing - it connects fine ( we are using System DSNs, by
> the way ). But if I launch MS Access and open a form that connects to
> MySQL, I get the error: 'execution of this application has produced a
> runtime error' and Access closes. Unfortunately, the 'runtime' version
> of Access doesn't allow you to open tables directly, or inspect any
> code-generated errors - it simply closes itself at the first sign of
> trouble. I can't reproduce the error on my system.
>
> Installation procedure:
>
> - log in as administrator
> - remove MyODBC via add / remove wizard
> - open windows explorer, select the 'winnt' folder, right-click,
> 'search' for myodbc and delete all files found
> - click on downloaded MyODBC MSI installer
> - test connection in ODBC administrator
>
> I've repeated this process a number of times on my PC and on some of the
> 'problem' PCs. I can't get the problem ones to work, and I can't get
> mine to give a problem.
>
> Some of the other testing PCs ( that worked fine, hence the site-wide
> upgrade ) are set up *identically* to the problem PCs - runtime version
> of Access, same NT domain security settings, etc. Admittedly the MS
> Access front-ends were different, but I don't see how that would give
> any issues - all the front-ends work in the same way ... mostly simple
> forms with linked tables.
>
> I have also tried both versions of MyODBC-3.51.10 - the original and the
> -2 version. Same problem.
>
> If I *must*, I can try to assemble a small test case that causes the
> problem. I've obviously moved everyone back to MyODBC-3.51.9 now ( a
> lengthy process ), and I don't have any spare PCs, so further testing is
> going to be an out-of-hours job.
>
> Let the lone system administrator beware :)
>
> --
> Daniel Kasak
> IT Developer
> NUS Consulting Group
> Level 5, 77 Pacific Highway
> North Sydney, NSW, Australia 2060
> T: (+61) 2 9922-7676 / F: (+61) 2 9922 7989
> email: dkasak [at] nusconsulting.com.au
> website: http://www.nusconsulting.com.au
>
>


------------------------------------------------------------ ----------------
----


> --
> MySQL ODBC Mailing List
> For list archives: http://lists.mysql.com/myodbc
> To unsubscribe: http://lists.mysql.com/myodbc?unsub=mberman [at] ivesinc.com



--
MySQL ODBC Mailing List
For list archives: http://lists.mysql.com/myodbc
To unsubscribe: http://lists.mysql.com/myodbc?unsub=gcdmo-myodbc [at] m.gmane.org

------------=_1106259878-24862-126
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Daniel Zur wrote:

>Hi Daniel,
>
>had a similar problem with a "normal" i.e. not the runtime version of
>Access. I wanted to deploy the database from my machine (DSN server in
>this case localhost) to a server 192.something. It took me several
>days to find out (maybe to easy to be in the documentation) that you
>can specify a new DSN string but then have to use the method RefreshLink to
>make it permanent. Don't know whether this fits to your problem or
>whether I am too dumb to really get the problem, but if my description
>sounds like a solution to your problem, I can offer some code to
>reestablish the connection. So let me know if you are interested.
>
>Best regards
>
>Daniel
>Business Consultancy Service
>
>

Thanks for the tips. I'll try it out - just out of interest - later
today when I can get some time on one of the problem PCs.
I've already got some code lying around to refresh linked tables. I used
to have to do this for Access machines running under Crossover Office (
testing only - we didn't go ahead with this project ).

Anyway, I think I'll hold off on another rollout for now. Last upgrade
bit me hard.

--
Daniel Kasak
IT Developer
NUS Consulting Group
Level 5, 77 Pacific Highway
North Sydney, NSW, Australia 2060
T: (+61) 2 9922-7676 / F: (+61) 2 9922 7989
email: dkasak [at] nusconsulting.com.au
website: http://www.nusconsulting.com.au


------------=_1106259878-24862-126
Content-Type: text/plain; charset=us-ascii

--
MySQL ODBC Mailing List
For list archives: http://lists.mysql.com/myodbc
To unsubscribe: http://lists.mysql.com/myodbc?unsub=gcdmo-myodbc [at] m.gmane.org
------------=_1106259878-24862-126--

Unfortunately our testing did not show this problem before release.
Currently working on a fix for SQLDriverConnect. Will publish to
www.mysql.com soon.

Mikhail Berman wrote:

>Daniel,
>
>I have the similar setup , only my development machine is Windows XP.
>
>Every morning in order to use MS-Access connected to MySQL, after MS-Access
>was close previous evening, I have to refresh all linked tables using
>"Linked tables manager".
>
>It seems to me that in your runtime versions of the application you might
>need to code abilitiy to resfresh all linked tables before use.
>
>Regards,
>
>Mikhail
>
>


--
Peter Harvey, Software Developer
MySQL AB, www.mysql.com

Are you MySQL certified? www.mysql.com/certification



--
MySQL ODBC Mailing List
For list archives: http://lists.mysql.com/myodbc
To unsubscribe: http://lists.mysql.com/myodbc?unsub=gcdmo-myodbc [at] m.gmane.org