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 7  2979 
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?
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
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
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
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
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
"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". This thread has been closed and replies have been disabled. Please start a new discussion. Similar topics
by: Katuil Katuil |
last post by:
Hello All:
Have a problem that I have never seen before and have not found anything
on
technet on how to resolve it. I have a SQL Server 2000 server that I
have
created a new database. I then...
|
by: Andreas Lauffer |
last post by:
I use Blanks in ColumnNames ( I know that this isnīt very good, but a
lot of code and querys had to be changed if I would remove all blanks
in all columnnames).
When I link this tables with ODBC...
|
by: Eric E |
last post by:
Hi all,
I'm having quite a bit of trouble with code to create linked tables in
Access 2K. I create a DAO tabledef using CreateTableDef against a DAO
database object, then set its connection...
|
by: Joe |
last post by:
I am using Access 2003 and are linking to an Oracle 9i ODBC datasource
(using Oracle ODBC drivers). After linking the tables in Access, I inspect
the data contained in the linked tables. For...
|
by: Tim Marshall |
last post by:
Hi folks.
In A2003, I am sometimes getting an error when I try to open a pass
through query or display, via DAO, field information from an ODBC
connected table. I've never generated this error...
|
by: ramazan_ozturk |
last post by:
I have the following problem with Access 2003, hopefully someone can
help.
I'm using MS Office Pro. 2003 on a Windows XP Pro. SP2 machine.
When I try to get external data import/link a table I...
|
by: Simon Bailey |
last post by:
In VC++6 I used to use the add member variable tab of the class wizard to
bind recordset fields with dialog controls simply by specifying the m_pSet->
variable before the variable name. This all...
|
by: rdemyan via AccessMonster.com |
last post by:
I just got Access 2003 and have been playing around with it. This whole
macro security thing can be a bit annoying.
Initially, I was able to link to my backends located on a second computer....
|
by: rdemyan via AccessMonster.com |
last post by:
With A2003, I'm having trouble accessing files in a folder on another
computer where back-end files, update files, etc are located. Here's the
scenario:
1) Computer #1 - A2003
2) Computer #2 -...
|
by: DJRhino |
last post by:
Was curious if anyone else was having this same issue or not....
I was just Up/Down graded to windows 11 and now my access combo boxes are not acting right. With win 10 I could start typing...
|
by: Aliciasmith |
last post by:
In an age dominated by smartphones, having a mobile app for your business is no longer an option; it's a necessity. Whether you're a startup or an established enterprise, finding the right mobile app...
|
by: tracyyun |
last post by:
Hello everyone,
I have a question and would like some advice on network connectivity. I have one computer connected to my router via WiFi, but I have two other computers that I want to be able to...
|
by: NeoPa |
last post by:
Hello everyone.
I find myself stuck trying to find the VBA way to get Access to create a PDF of the currently-selected (and open) object (Form or Report).
I know it can be done by selecting :...
|
by: Teri B |
last post by:
Hi, I have created a sub-form Roles. In my course form the user selects the roles assigned to the course.
0ne-to-many. One course many roles.
Then I created a report based on the Course form and...
|
by: nia12 |
last post by:
Hi there,
I am very new to Access so apologies if any of this is obvious/not clear.
I am creating a data collection tool for health care employees to complete. It consists of a number of...
|
by: NeoPa |
last post by:
Introduction
For this article I'll be focusing on the Report (clsReport) class. This simply handles making the calling Form invisible until all of the Reports opened by it have been closed, when it...
|
by: isladogs |
last post by:
The next online meeting of the Access Europe User Group will be on Wednesday 6 Dec 2023 starting at 18:00 UK time (6PM UTC) and finishing at about 19:15 (7.15PM).
In this month's session, Mike...
|
by: GKJR |
last post by:
Does anyone have a recommendation to build a standalone application to replace an Access database? I have my bookkeeping software I developed in Access that I would like to make available to other...
| |
