[thelist] Self-expiring data sources in CFMX?

[Jeff Haas]

Hi.

I'm having a weird problem with CFMX that I haven't run into before on any platform. I'm developing a MX application with an Access database on a server hosted on a shared box in Ottawa and have configured my DSNs with their web-based control panel. Nothing out of the ordinary here. Just the regular stuff.

The problem is that the DSN self-expires every few days. It just stops being accessible to CF, but remains registered as a system DSN. I have to delete the DSN and set it up again in order to get CF to work properly.

I've asked tech support about it and they say it's a common problem with MX for which there is no solution. I can't believe that. Has anyone else run into it? If so, how did you resolve it?

The host says that people who have been complaining about it (and I got the impression that there have been numerous complaints) have just been moved to a CF5 server. I'd rather not do that, but do I have any other choice?

Can anyone here share some information on this?

Thanx.

Jeff



Jeffrey Haas
Manager, Technical Development, Digital Media
Spencer Francey Peters
t: 416.203.2300
f: 416.203.0303
e: jhaas at sfpinc.com


Jeffrey Haas
Manager, Technical Development, Digital Media
Spencer Francey Peters
t: 416.203.2300
f: 416.203.0303
e: jhaas at sfpinc.com