473,695 Members | 2,360 Online
Bytes | Software Development & Data Engineering Community
+ Post

Home Posts Topics Members FAQ

Linking to ODBC in A2003 aborts

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
7 3057
On Nov 2, 10:02 am, Salad <o...@vinegar.c omwrote:
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.microso ft.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=lNVwwum NnqU
Maybe the Access install is corrupted?? Do a re-install?

Nov 2 '07 #2
Technolust wrote:
On Nov 2, 10:02 am, Salad <o...@vinegar.c omwrote:
>>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
difficultie s in A2003. I'm trying to follow the instructions inhttp://support.microso ft.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=lNVwwum NnqU


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
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.co mwrote in message
news:13******** *****@corp.supe rnews.com...
Technolust wrote:
>On Nov 2, 10:02 am, Salad <o...@vinegar.c omwrote:
>>>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
difficulti es in A2003. I'm trying to follow the instructions
inhttp://support.microso ft.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?

Connectedhtt p://www.youtube.com/watch?v=lNVwwum NnqU


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
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.co mwrote in message
news:13******** *****@corp.supe rnews.com...
>>Technolust wrote:

>>>On Nov 2, 10:02 am, Salad <o...@vinegar.c omwrote:
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
difficultie s in A2003. I'm trying to follow the instructions
inhttp://support.microso ft.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?

Connectedht tp://www.youtube.com/watch?v=lNVwwum NnqU
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
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.co mwrote in message
news:13******** *****@corp.supe rnews.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.co mwrote in message
news:13******* ******@corp.sup ernews.com...
>>>Technolust wrote:
On Nov 2, 10:02 am, Salad <o...@vinegar.c omwrote:
>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
>difficulti es in A2003. I'm trying to follow the instructions
>inhttp://support.microso ft.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
>presente d with a window to select the source.
>
>Does A2003 require something "extra" to permit the selection of ODBC
>data sources?
>
>Connectedh ttp://www.youtube.com/watch?v=lNVwwum NnqU
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
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.co mwrote in message
news:13******** *****@corp.supe rnews.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.co mwrote in message
news:13***** ********@corp.s upernews.com...
Technolus t wrote:

>On Nov 2, 10:02 am, Salad <o...@vinegar.c omwrote:
>
>
>
>>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
>>difficult ies in A2003. I'm trying to follow the instructions
>>inhttp://support.microso ft.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
>>present ed 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=lNVwwum NnqU
>
>
>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
"Salad" <oi*@vinegar.co mwrote
>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 thread has been closed and replies have been disabled. Please start a new discussion.

Similar topics

0
6941
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 used DTS to import data from a MS Access 97 database. Before making the import, I made changes to the MS Access database
2
1853
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 in my ACC97 - project, some of the tables causes an ODBC-Error. Are there possibilities to workaround this error? Thanks, Andreas Lauffer, easySoft. GmbH, Germany
4
13486
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 string appropriately. The trouble is when I go to append the tableDef to the collection I get error 3264: No field defined --cannot append TableDef or Index Any suggestions?
7
11831
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 tables that involve a number field as the primary key, the data is returned successfully. For tables that involve a character field (e.g. CHAR(3) or VARCHAR(10)) as the primary key, I have the correct number of rows returned, but the data displayed...
1
4572
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 in A97 apps and, indeed, this is happening on A2003 apps converted from very robust A97 apps that operated for years (and still operate) reliably. The error is:
1
1621
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 don't have the option for the file type ODBC instead i see a option Registry error. Does anyone know what the problem is? Thanks in advance.
1
1133
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 appears to have changed in VC ..NET. I have a dialog - IDD_DATABASE_FORM with an edit box IDC_PRODUCTID. I wish to bind this control through the view class CDatabaseView to the ODBC recordset CDBProductSet. I notice that there is a function...
3
1925
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. Then after I compacted the backends on the other computer and I think I also tired of the macro security message on Access 2003 and selected to not run unsafe expressions. Now I cannot link to the backends on the second computer from the computer...
17
3142
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 - Access 2000; folder with back-ends for both computers and 'Update' folder. I have a launcher program that launces my application (MyApp). The launcher program also checks for updates to MyApp located in 'Update' folder (on
0
8647
marktang
by: marktang | last post by:
ONU (Optical Network Unit) is one of the key components for providing high-speed Internet services. Its primary function is to act as an endpoint device located at the user's premises. However, people are often confused as to whether an ONU can Work As a Router. In this blog post, we’ll explore What is ONU, What Is Router, ONU & Router’s main usage, and What is the difference between ONU and Router. Let’s take a closer look ! Part I. Meaning of...
0
8585
by: Hystou | last post by:
Most computers default to English, but sometimes we require a different language, especially when relocating. Forgot to request a specific language before your computer shipped? No problem! You can effortlessly switch the default language on Windows 10 without reinstalling. I'll walk you through it. First, let's disable language synchronization. With a Microsoft account, language settings sync across devices. To prevent any complications,...
0
9132
Oralloy
by: Oralloy | last post by:
Hello folks, I am unable to find appropriate documentation on the type promotion of bit-fields when using the generalised comparison operator "<=>". The problem is that using the GNU compilers, it seems that the internal comparison operator "<=>" tries to promote arguments from unsigned to signed. This is as boiled down as I can make it. Here is my compilation command: g++-12 -std=c++20 -Wnarrowing bit_field.cpp Here is the code in...
1
8864
by: Hystou | last post by:
Overview: Windows 11 and 10 have less user interface control over operating system update behaviour than previous versions of Windows. In Windows 11 and 10, there is no way to turn off the Windows Update option using the Control Panel or Settings app; it automatically checks for updates and installs any it finds, whether you like it or not. For most users, this new feature is actually very convenient. If you want to control the update process,...
0
8838
tracyyun
by: tracyyun | last post by:
Dear forum friends, With the development of smart home technology, a variety of wireless communication protocols have appeared on the market, such as Zigbee, Z-Wave, Wi-Fi, Bluetooth, etc. Each protocol has its own unique characteristics and advantages, but as a user who is planning to build a smart home system, I am a bit confused by the choice of these technologies. I'm particularly interested in Zigbee because I've heard it does some...
0
7682
agi2029
by: agi2029 | last post by:
Let's talk about the concept of autonomous AI software engineers and no-code agents. These AIs are designed to manage the entire lifecycle of a software development project—planning, coding, testing, and deployment—without human intervention. Imagine an AI that can take a project description, break it down, write the code, debug it, and then launch it, all on its own.... Now, this would greatly impact the work of software developers. The idea...
1
6506
isladogs
by: isladogs | last post by:
The next Access Europe User Group meeting will be on Wednesday 1 May 2024 starting at 18:00 UK time (6PM UTC+1) and finishing by 19:30 (7.30PM). In this session, we are pleased to welcome a new presenter, Adolph Dupré who will be discussing some powerful techniques for using class modules. He will explain when you may want to use classes instead of User Defined Types (UDT). For example, to manage the data in unbound forms. Adolph will...
0
5842
by: conductexam | last post by:
I have .net C# application in which I am extracting data from word file and save it in database particularly. To store word all data as it is I am converting the whole word file firstly in HTML and then checking html paragraph one by one. At the time of converting from word file to html my equations which are in the word document file was convert into image. Globals.ThisAddIn.Application.ActiveDocument.Select();...
0
4592
by: adsilva | last post by:
A Windows Forms form does not have the event Unload, like VB6. What one acts like?

By using Bytes.com and it's services, you agree to our Privacy Policy and Terms of Use.

To disable or enable advertisements and analytics tracking please visit the manage ads & tracking page.