Login ProductsSalesSupportDownloadsAbout |
Home » Technical Support » DBISAM Technical Support » Support Forums » DBISAM ODBC Driver » View Thread |
Messages 1 to 10 of 10 total |
Access XP (2002) closes down abruptly |
Wed, Apr 12 2006 3:24 AM | Permanent Link |
"Ian Turner" | On the 26th March 2003, J. Michael Eubanks posted this problem ...
<< We have a customer who is trying to link DBISAM tables into Access XP. When they attempt to link Access shuts down with no errors. We are able to access the data (same table and database) using Excel, and Access is able to import the data with no problems but linking the data is a problem. Any help would be greatly appriciated. Operating System: Windows XP Professional (SP1) Access Version: Access XP Data Access: Local ODBC Driver Version: 3.24 (Read Only) >> I am having exactly the same problem as this with Access XP (2002) the current versions of the ODBC driver, both full access and read only. About 20-30 seconds after having made a link to a DBISAM table Access quietly shuts down with no by your leave. However, I can import the data into Access tables rather than link to the DBISAM sources I have tried versions 4.20 and 4.22b5 of the ODBC drivers (all I had with me at the customers). Was there any resolution to this problem? many thanks, Ian Turner |
Wed, Apr 12 2006 7:02 AM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Ian,
<< I am having exactly the same problem as this with Access XP (2002) the current versions of the ODBC driver, both full access and read only. About 20-30 seconds after having made a link to a DBISAM table Access quietly shuts down with no by your leave. However, I can import the data into Access tables rather than link to the DBISAM sources I have tried versions 4.20 and 4.22b5 of the ODBC drivers (all I had with me at the customers). Was there any resolution to this problem? >> We have had several reports of this problem with Access, and have no idea how or what is causing the problem. It happens randomly, and as far as I can tell, it doesn't have anything to do with our ODBC driver, but rather something to do with Access. I've had it happen a couple of times here, but it doesn't happen consistently, nor is there a proper AV, error message, etc. I've never seen DBISAM have an error that didn't generate at least an AV or runtime error message. A Google Groups search turns up a similar issue with Access 2000 and 2002: http://support.microsoft.com/?id=319491 However, I'm not sure if this is the same issue that we're seeing. -- Tim Young Elevate Software www.elevatesoft.com |
Fri, Apr 14 2006 4:44 AM | Permanent Link |
"GregF" | "Tim Young [Elevate Software]" <timyoung@elevatesoft.com> wrote in message news:B11A29B7-6383-4915-B57C-FB949A39FA15@news.elevatesoft.com... > Ian, > > << I am having exactly the same problem as this with Access XP (2002) the current versions of the ODBC driver, both full access > and read only. About 20-30 seconds after having made a link to a DBISAM table Access quietly shuts down with no by your leave. > However, I can import the data into Access tables rather than link to the DBISAM sources > > I have tried versions 4.20 and 4.22b5 of the ODBC drivers (all I had with me at the customers). > > Was there any resolution to this problem? >> > > We have had several reports of this problem with Access, and have no idea how or what is causing the problem. It happens > randomly, and as far as I can tell, it doesn't have anything to do with our ODBC driver, but rather something to do with Access. > I've had it happen a couple of times here, but it doesn't happen consistently, nor is there a proper AV, error message, etc. I've > never seen DBISAM have an error that didn't generate at least an AV or runtime error message. > > A Google Groups search turns up a similar issue with Access 2000 and 2002: > > http://support.microsoft.com/?id=319491 > > However, I'm not sure if this is the same issue that we're seeing. > > -- > Tim Young > Elevate Software > www.elevatesoft.com > > it seems to only happen in my experience if you do not "touch" any database object within a certain short period of starting Access also i have never had it happen if the Access DB has an "internal" table as well as ODBC links. gregF |
Fri, Apr 14 2006 11:51 AM | Permanent Link |
"Ian Turner" | "GregF" <footyfacts@yahoo.com> wrote in message news:F1E5CD45-2D40-4A54-8793-7A9695C63317@news.elevatesoft.com... > it seems to only happen in my experience > if you do not "touch" any database object > within a certain short period of starting Access > also i have never had it happen if the Access DB > has an "internal" table as well as ODBC links. > > gregF > Many thanks for that Greg. I will try creating a dummy table in the database. Ian |
Fri, Apr 14 2006 3:39 PM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Greg,
<< it seems to only happen in my experience if you do not "touch" any database object within a certain short period of starting Access also i have never had it happen if the Access DB has an "internal" table as well as ODBC links. >> Many thanks for the info. I will test this out and see if that is the situation, and if it is, I'll see what kind of a workaround I can come up with. -- Tim Young Elevate Software www.elevatesoft.com |
Mon, Apr 17 2006 1:06 AM | Permanent Link |
"GregF" | "Tim Young [Elevate Software]" <timyoung@elevatesoft.com> wrote in message news:6A906B2A-8A6B-4781-8A41-1DAF1943DE28@news.elevatesoft.com... > Greg, > > << it seems to only happen in my experience if you do not "touch" any database object within a certain short period of starting > Access also i have never had it happen if the Access DB has an "internal" table as well as ODBC links. >> > > Many thanks for the info. I will test this out and see if that is the situation, and if it is, I'll see what kind of a workaround > I can come up with. > > -- > Tim Young > Elevate Software > www.elevatesoft.com > > personally though I think it is an Access problem with an ODBC database rather than a specific DBISAM error. I haven't used it much because it always requires a refresh of the ODBC source every time. Am I doing something wrong in how I am linking to the tables? gregF |
Mon, Apr 17 2006 7:17 AM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Greg,
<< I haven't used it much because it always requires a refresh of the ODBC source every time. Am I doing something wrong in how I am linking to the tables? >> When you say "it", do you mean Access itself ? Also, are you talking about refreshing the underlying DBISAM tables, or the presence of the ODBC data source itself ? Normally you shouldn't have to do anything in terms of refreshing a DBISAM table via a link other than simply performing a Records/Refresh in Access. That should do the trick. -- Tim Young Elevate Software www.elevatesoft.com |
Wed, Apr 19 2006 7:39 PM | Permanent Link |
"Ian Turner" | "Ian Turner" <it@acssoftware.co.uk> wrote in message
news:2AE2DEB5-264C-42BB-A4A4-49DB2737DFBE@news.elevatesoft.com... > > "GregF" <footyfacts@yahoo.com> wrote in message > news:F1E5CD45-2D40-4A54-8793-7A9695C63317@news.elevatesoft.com... > > it seems to only happen in my experience > > if you do not "touch" any database object > > within a certain short period of starting Access > > also i have never had it happen if the Access DB > > has an "internal" table as well as ODBC links. > > > > gregF > > > > Many thanks for that Greg. I will try creating a dummy table in the > database. > > Ian My customer tried creating a 'internal' Access table with a couple of fields and a few records but unfortunately no discernable difference; still shuts down without any comment, sometimes within a matter of a few seconds after loading the database. Looks like it's back to the drawing board. Ian |
Thu, Apr 20 2006 5:40 AM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Ian,
<< My customer tried creating a 'internal' Access table with a couple of fields and a few records but unfortunately no discernable difference; still shuts down without any comment, sometimes within a matter of a few seconds after loading the database. >> Could you possibly find out the version number of Access that they're using ? I'm trying to correlate the problem to a specific version, but so far haven't had much luck. Also, did the customer turn off the AutoCorrect feature per the link that I posted ? I'm not sure if it has anything to do with this, but it is worth a shot. -- Tim Young Elevate Software www.elevatesoft.com |
Thu, Apr 20 2006 7:13 AM | Permanent Link |
"Ian Turner" | "Tim Young [Elevate Software]" <timyoung@elevatesoft.com> wrote in message
news:4CD65043-7E4E-4233-AF8B-9B49C51C5120@news.elevatesoft.com... > Ian, > > << My customer tried creating a 'internal' Access table with a couple of > fields and a few records but unfortunately no discernable difference; still > shuts down without any comment, sometimes within a matter of a few seconds > after loading the database. >> > > Could you possibly find out the version number of Access that they're using > ? I'm trying to correlate the problem to a specific version, but so far > haven't had much luck. Also, did the customer turn off the AutoCorrect > feature per the link that I posted ? I'm not sure if it has anything to do > with this, but it is worth a shot. > The Access version number is 10.2616.2625. I will check on the AutoCorrect and get back to you. Ian |
This web page was last updated on Friday, April 26, 2024 at 05:32 PM | Privacy PolicySite Map © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ? E-mail us at info@elevatesoft.com |