By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
424,694 Members | 2,015 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 424,694 IT Pros & Developers. It's quick & easy.

Linking to ODBC in A2003 aborts

P: n/a
I am converting an application from A97 to A2003. I have 2 tables
created by another application as a Foxpro.dbf. The table has no index.

The connect string in A97 is
FoxPro 2.0;HDR=NO;IMEX=2;DATABASE=C:\Test

It's really easy to connect to those tables in A97. I'm having
difficulties in A2003. I'm trying to follow the instructions in
http://support.microsoft.com/kb/824264/.

When I do a File/GetExternalData/Link in A2003 I select OCDB Databases()
in the files of type. As soon as I select that option type the dialog
box for linking the tables shuts down/closes. I have no opportunity to
select an ODBC data source.

This does not occur in A97. When I select ODBC Databases, I am
presented with a window to select the source.

Does A2003 require something "extra" to permit the selection of ODBC
data sources?

Connected
http://www.youtube.com/watch?v=lNVwwumNnqU
Nov 2 '07 #1
Share this Question
Share on Google+
7 Replies


P: n/a
On Nov 2, 10:02 am, Salad <o...@vinegar.comwrote:
I am converting an application from A97 to A2003. I have 2 tables
created by another application as a Foxpro.dbf. The table has no index.

The connect string in A97 is
FoxPro 2.0;HDR=NO;IMEX=2;DATABASE=C:\Test

It's really easy to connect to those tables in A97. I'm having
difficulties in A2003. I'm trying to follow the instructions inhttp://support.microsoft.com/kb/824264/.

When I do a File/GetExternalData/Link in A2003 I select OCDB Databases()
in the files of type. As soon as I select that option type the dialog
box for linking the tables shuts down/closes. I have no opportunity to
select an ODBC data source.

This does not occur in A97. When I select ODBC Databases, I am
presented with a window to select the source.

Does A2003 require something "extra" to permit the selection of ODBC
data sources?

Connectedhttp://www.youtube.com/watch?v=lNVwwumNnqU
Maybe the Access install is corrupted?? Do a re-install?

Nov 2 '07 #2

P: n/a
Technolust wrote:
On Nov 2, 10:02 am, Salad <o...@vinegar.comwrote:
>>I am converting an application from A97 to A2003. I have 2 tables
created by another application as a Foxpro.dbf. The table has no index.

The connect string in A97 is
FoxPro 2.0;HDR=NO;IMEX=2;DATABASE=C:\Test

It's really easy to connect to those tables in A97. I'm having
difficulties in A2003. I'm trying to follow the instructions inhttp://support.microsoft.com/kb/824264/.

When I do a File/GetExternalData/Link in A2003 I select OCDB Databases()
in the files of type. As soon as I select that option type the dialog
box for linking the tables shuts down/closes. I have no opportunity to
select an ODBC data source.

This does not occur in A97. When I select ODBC Databases, I am
presented with a window to select the source.

Does A2003 require something "extra" to permit the selection of ODBC
data sources?

Connectedhttp://www.youtube.com/watch?v=lNVwwumNnqU


Maybe the Access install is corrupted??
Thanks for your response.

It could be. However, the application, and Access 2003, seems to run
OK. The only thing I've done recently is install VSTO.

I noticed something funny. My connect string in A97 is
FoxPro 2.0;HDR=NO;IMEX=2;DATABASE=C:\Test

I have an old FoxPro DOS 2.6 on my computer. If I attempt to open those
dbf files with FoxPro 2.6 it says it's not a database file. If they
were 2.0 files I'd think my 2.6 version would see and recognize them.

If I attempt to open them with A2003 as a Dbase III, Dbase IV, or Dbase
IV it tells me the External table's not in the expected format.

I opened the dbf table in A97 and exported it to a text file.
Fortunately A2003 can recognize a text file. I may need to tell the
developer to create the files as text files instead.

I'm really disappointed in MS. I'd like to think their programs work
together. I expect upgrading to make things better, not add headaches.
>Do a re-install?
As a last resort.
Fire
http://www.youtube.com/watch?v=Ye0k-qRDSno
Nov 2 '07 #3

P: n/a
Are these files still being created / updated with the other application?

If not, then export them as Access tables from Access 97 and link/import
them into Access 2003.

I can imagine that support for older versions might have been dropped
between Access 97 and 2003, but I don't do much with either Fox or dBase
files, so don't know for sure.

If you have a problem reading them with a later version of FoxPro, I
wouldn't think that a reinstall of Access 2003 is likely to help -- that's
usually a final, desperation try (and usually doesn't solve whatever problem
brought on the desperation -- which is not to say that it never is
successful).

Larry Linson
Microsoft Access MVP
"Salad" <oi*@vinegar.comwrote in message
news:13*************@corp.supernews.com...
Technolust wrote:
>On Nov 2, 10:02 am, Salad <o...@vinegar.comwrote:
>>>I am converting an application from A97 to A2003. I have 2 tables
created by another application as a Foxpro.dbf. The table has no index.

The connect string in A97 is
FoxPro 2.0;HDR=NO;IMEX=2;DATABASE=C:\Test

It's really easy to connect to those tables in A97. I'm having
difficulties in A2003. I'm trying to follow the instructions
inhttp://support.microsoft.com/kb/824264/.

When I do a File/GetExternalData/Link in A2003 I select OCDB Databases()
in the files of type. As soon as I select that option type the dialog
box for linking the tables shuts down/closes. I have no opportunity to
select an ODBC data source.

This does not occur in A97. When I select ODBC Databases, I am
presented with a window to select the source.

Does A2003 require something "extra" to permit the selection of ODBC
data sources?

Connectedhttp://www.youtube.com/watch?v=lNVwwumNnqU


Maybe the Access install is corrupted??

Thanks for your response.

It could be. However, the application, and Access 2003, seems to run OK.
The only thing I've done recently is install VSTO.

I noticed something funny. My connect string in A97 is
FoxPro 2.0;HDR=NO;IMEX=2;DATABASE=C:\Test

I have an old FoxPro DOS 2.6 on my computer. If I attempt to open those
dbf files with FoxPro 2.6 it says it's not a database file. If they were
2.0 files I'd think my 2.6 version would see and recognize them.

If I attempt to open them with A2003 as a Dbase III, Dbase IV, or Dbase IV
it tells me the External table's not in the expected format.

I opened the dbf table in A97 and exported it to a text file. Fortunately
A2003 can recognize a text file. I may need to tell the developer to
create the files as text files instead.

I'm really disappointed in MS. I'd like to think their programs work
together. I expect upgrading to make things better, not add headaches.
>>Do a re-install?

As a last resort.
Fire
http://www.youtube.com/watch?v=Ye0k-qRDSno

Nov 2 '07 #4

P: n/a
Larry Linson wrote:
Are these files still being created / updated with the other application?

If not, then export them as Access tables from Access 97 and link/import
them into Access 2003.

I can imagine that support for older versions might have been dropped
between Access 97 and 2003, but I don't do much with either Fox or dBase
files, so don't know for sure.

If you have a problem reading them with a later version of FoxPro, I
wouldn't think that a reinstall of Access 2003 is likely to help -- that's
usually a final, desperation try (and usually doesn't solve whatever problem
brought on the desperation -- which is not to say that it never is
successful).
These files are created from an external accounting program. They're
recognized by A97 but then A97 has FoxPro in the "Files of type"
dropdown. If I select "ODBC Databases ()" in A97 the next window that
pops up is the datasource window so the ODBC works as expected.

In A2003, since there is no FoxPro, I guess my only option is ODBC.
However, when I select "ODBC Databases ()" file types the datasource
window isn't displayed...it simply returns to the database window as if
the linking process is complete although no data source was selected.

This doesn't seem normal. I suppose if I ever needed to link to SQL
Server I'd have to buy a new computer and install Access on it.

Thanks for your suggestions.
>
Larry Linson
Microsoft Access MVP
"Salad" <oi*@vinegar.comwrote in message
news:13*************@corp.supernews.com...
>>Technolust wrote:

>>>On Nov 2, 10:02 am, Salad <o...@vinegar.comwrote:
I am converting an application from A97 to A2003. I have 2 tables
created by another application as a Foxpro.dbf. The table has no index.

The connect string in A97 is
FoxPro 2.0;HDR=NO;IMEX=2;DATABASE=C:\Test

It's really easy to connect to those tables in A97. I'm having
difficulties in A2003. I'm trying to follow the instructions
inhttp://support.microsoft.com/kb/824264/.

When I do a File/GetExternalData/Link in A2003 I select OCDB Databases()
in the files of type. As soon as I select that option type the dialog
box for linking the tables shuts down/closes. I have no opportunity to
select an ODBC data source.

This does not occur in A97. When I select ODBC Databases, I am
presented with a window to select the source.

Does A2003 require something "extra" to permit the selection of ODBC
data sources?

Connectedhttp://www.youtube.com/watch?v=lNVwwumNnqU
Maybe the Access install is corrupted??

Thanks for your response.

It could be. However, the application, and Access 2003, seems to run OK.
The only thing I've done recently is install VSTO.

I noticed something funny. My connect string in A97 is
FoxPro 2.0;HDR=NO;IMEX=2;DATABASE=C:\Test

I have an old FoxPro DOS 2.6 on my computer. If I attempt to open those
dbf files with FoxPro 2.6 it says it's not a database file. If they were
2.0 files I'd think my 2.6 version would see and recognize them.

If I attempt to open them with A2003 as a Dbase III, Dbase IV, or Dbase IV
it tells me the External table's not in the expected format.

I opened the dbf table in A97 and exported it to a text file. Fortunately
A2003 can recognize a text file. I may need to tell the developer to
create the files as text files instead.

I'm really disappointed in MS. I'd like to think their programs work
together. I expect upgrading to make things better, not add headaches.

>>>Do a re-install?

As a last resort.
Fire
http://www.youtube.com/watch?v=Ye0k-qRDSno


Nov 3 '07 #5

P: n/a
Do you have an ODBC driver for FoxPro installed?

As there appears to be no direct option for "FoxPro" in Access 2002 (I'm
temporarily reverted to that version to expedite using Speed Ferret in a
current project), I tried ODBC, and there were two listings for FoxPro...
one "Visual FoxPro Database (not sharable).dsn" and the other "Visual FoxPro
Tables (not sharable).dsn". When I try to select either, it fails with an
ODBC Error. Those could appear because Access 97 was installed on this
machine, and never uninstalled, although later installs of Access 2002 and
2003 made it unusable, or something could have been installed / registry
settings modified by some third-party application.

As far as I know, I have no FoxPro files of either type on the machine...
perhaps that is why the call fails, or perhaps the "(not sharable)" on those
listings means that use is limited in some way.

Larry Linson
Microsoft Access MVP
"Salad" <oi*@vinegar.comwrote in message
news:13*************@corp.supernews.com...
Larry Linson wrote:
>Are these files still being created / updated with the other application?

If not, then export them as Access tables from Access 97 and link/import
them into Access 2003.

I can imagine that support for older versions might have been dropped
between Access 97 and 2003, but I don't do much with either Fox or dBase
files, so don't know for sure.

If you have a problem reading them with a later version of FoxPro, I
wouldn't think that a reinstall of Access 2003 is likely to help --
that's usually a final, desperation try (and usually doesn't solve
whatever problem brought on the desperation -- which is not to say that
it never is successful).

These files are created from an external accounting program. They're
recognized by A97 but then A97 has FoxPro in the "Files of type" dropdown.
If I select "ODBC Databases ()" in A97 the next window that pops up is the
datasource window so the ODBC works as expected.

In A2003, since there is no FoxPro, I guess my only option is ODBC.
However, when I select "ODBC Databases ()" file types the datasource
window isn't displayed...it simply returns to the database window as if
the linking process is complete although no data source was selected.

This doesn't seem normal. I suppose if I ever needed to link to SQL
Server I'd have to buy a new computer and install Access on it.

Thanks for your suggestions.
>>
Larry Linson
Microsoft Access MVP
"Salad" <oi*@vinegar.comwrote in message
news:13*************@corp.supernews.com...
>>>Technolust wrote:
On Nov 2, 10:02 am, Salad <o...@vinegar.comwrote:
>I am converting an application from A97 to A2003. I have 2 tables
>created by another application as a Foxpro.dbf. The table has no
>index.
>
>The connect string in A97 is
FoxPro 2.0;HDR=NO;IMEX=2;DATABASE=C:\Test
>
>It's really easy to connect to those tables in A97. I'm having
>difficulties in A2003. I'm trying to follow the instructions
>inhttp://support.microsoft.com/kb/824264/.
>
>When I do a File/GetExternalData/Link in A2003 I select OCDB
>Databases()
>in the files of type. As soon as I select that option type the dialog
>box for linking the tables shuts down/closes. I have no opportunity to
>select an ODBC data source.
>
>This does not occur in A97. When I select ODBC Databases, I am
>presented with a window to select the source.
>
>Does A2003 require something "extra" to permit the selection of ODBC
>data sources?
>
>Connectedhttp://www.youtube.com/watch?v=lNVwwumNnqU
Maybe the Access install is corrupted??

Thanks for your response.

It could be. However, the application, and Access 2003, seems to run OK.
The only thing I've done recently is install VSTO.

I noticed something funny. My connect string in A97 is
FoxPro 2.0;HDR=NO;IMEX=2;DATABASE=C:\Test

I have an old FoxPro DOS 2.6 on my computer. If I attempt to open those
dbf files with FoxPro 2.6 it says it's not a database file. If they were
2.0 files I'd think my 2.6 version would see and recognize them.

If I attempt to open them with A2003 as a Dbase III, Dbase IV, or Dbase
IV it tells me the External table's not in the expected format.

I opened the dbf table in A97 and exported it to a text file. Fortunately
A2003 can recognize a text file. I may need to tell the developer to
create the files as text files instead.

I'm really disappointed in MS. I'd like to think their programs work
together. I expect upgrading to make things better, not add headaches.
Do a re-install?

As a last resort.
Fire
http://www.youtube.com/watch?v=Ye0k-qRDSno

Nov 3 '07 #6

P: n/a
Larry Linson wrote:
Do you have an ODBC driver for FoxPro installed?
Hi Larry. It appears FoxPro had nothing to do with it. It was Norton
Anti-Virus. I started another thread regarding the solution.

Thanks for your response.
>
As there appears to be no direct option for "FoxPro" in Access 2002 (I'm
temporarily reverted to that version to expedite using Speed Ferret in a
current project), I tried ODBC, and there were two listings for FoxPro...
one "Visual FoxPro Database (not sharable).dsn" and the other "Visual FoxPro
Tables (not sharable).dsn". When I try to select either, it fails with an
ODBC Error. Those could appear because Access 97 was installed on this
machine, and never uninstalled, although later installs of Access 2002 and
2003 made it unusable, or something could have been installed / registry
settings modified by some third-party application.

As far as I know, I have no FoxPro files of either type on the machine...
perhaps that is why the call fails, or perhaps the "(not sharable)" on those
listings means that use is limited in some way.

Larry Linson
Microsoft Access MVP
"Salad" <oi*@vinegar.comwrote in message
news:13*************@corp.supernews.com...
>>Larry Linson wrote:

>>>Are these files still being created / updated with the other application?

If not, then export them as Access tables from Access 97 and link/import
them into Access 2003.

I can imagine that support for older versions might have been dropped
between Access 97 and 2003, but I don't do much with either Fox or dBase
files, so don't know for sure.

If you have a problem reading them with a later version of FoxPro, I
wouldn't think that a reinstall of Access 2003 is likely to help --
that's usually a final, desperation try (and usually doesn't solve
whatever problem brought on the desperation -- which is not to say that
it never is successful).

These files are created from an external accounting program. They're
recognized by A97 but then A97 has FoxPro in the "Files of type" dropdown.
If I select "ODBC Databases ()" in A97 the next window that pops up is the
datasource window so the ODBC works as expected.

In A2003, since there is no FoxPro, I guess my only option is ODBC.
However, when I select "ODBC Databases ()" file types the datasource
window isn't displayed...it simply returns to the database window as if
the linking process is complete although no data source was selected.

This doesn't seem normal. I suppose if I ever needed to link to SQL
Server I'd have to buy a new computer and install Access on it.

Thanks for your suggestions.

>>Larry Linson
Microsoft Access MVP
"Salad" <oi*@vinegar.comwrote in message
news:13*************@corp.supernews.com...
Technolust wrote:

>On Nov 2, 10:02 am, Salad <o...@vinegar.comwrote:
>
>
>
>>I am converting an application from A97 to A2003. I have 2 tables
>>created by another application as a Foxpro.dbf. The table has no
>>index.
>>
>>The connect string in A97 is
> FoxPro 2.0;HDR=NO;IMEX=2;DATABASE=C:\Test
>>
>>It's really easy to connect to those tables in A97. I'm having
>>difficulties in A2003. I'm trying to follow the instructions
>>inhttp://support.microsoft.com/kb/824264/.
>>
>>When I do a File/GetExternalData/Link in A2003 I select OCDB
>>Databases()
>>in the files of type. As soon as I select that option type the dialog
>>box for linking the tables shuts down/closes. I have no opportunity to
>>select an ODBC data source.
>>
>>This does not occur in A97. When I select ODBC Databases, I am
>>presented with a window to select the source.
>>
>>Does A2003 require something "extra" to permit the selection of ODBC
>>data sources?
>>
>>Connectedhttp://www.youtube.com/watch?v=lNVwwumNnqU
>
>
>Maybe the Access install is corrupted??

Thanks for your response.

It could be. However, the application, and Access 2003, seems to run OK.
The only thing I've done recently is install VSTO.

I noticed something funny. My connect string in A97 is
FoxPro 2.0;HDR=NO;IMEX=2;DATABASE=C:\Test

I have an old FoxPro DOS 2.6 on my computer. If I attempt to open those
dbf files with FoxPro 2.6 it says it's not a database file. If they were
2.0 files I'd think my 2.6 version would see and recognize them.

If I attempt to open them with A2003 as a Dbase III, Dbase IV, or Dbase
IV it tells me the External table's not in the expected format.

I opened the dbf table in A97 and exported it to a text file. Fortunately
A2003 can recognize a text file. I may need to tell the developer to
create the files as text files instead.

I'm really disappointed in MS. I'd like to think their programs work
together. I expect upgrading to make things better, not add headaches.

>Do a re-install?

As a last resort.
Fire
http://www.youtube.com/watch?v=Ye0k-qRDSno

Nov 3 '07 #7

P: n/a
"Salad" <oi*@vinegar.comwrote
>Do you have an ODBC driver for FoxPro installed?

Hi Larry. It appears FoxPro had nothing to do with it. It was Norton
Anti-Virus. I started another thread regarding the solution.
I saw the other thread... Some time ago I used NAV, but haven't for some
time.

I'm using NOD32 from www.eset.com. I haven't had a virus infection since I
began using it over a year ago, it's unobtrusive, and, AFAIK, it doesn't
interfere with anything except the "bad stuff".
Nov 4 '07 #8

This discussion thread is closed

Replies have been disabled for this discussion.