Access version affecting data import

[Richard R3]

I am having trouble importing data @ work, and the problem seems to depend on
the version of Access I use. The troubles are the same, no matter if the
database is new/blank, or if it is an older database already having been
created & used by others. The problem seems to be isolated to the task of
changing field types during the import proccess--when I click each
column/field.

V2000 imports fine, and allows the changing of field types--but we would
like to update to V2003, as we have a new project coming up which we hope
will have all the new functionality & coding.

V2000 allows import but only allows the changing of field type for the first
field/column. When I select the other fields, the data type does not change
from what was selected for the first column--when you change the type, you
can see the first column is still the only one being changed.

V2003 is "broken". When I select the second column during the import
process, I get an error. It says, "There was an error loading an ActiveX
control on one of your forms or reports...The expression may not result in
the name of a macro, the name of a user-defined function, or [Event
Procedure]...There may have been an error evaluating the funtion, event, or
macro...{under more help--VBA encountered a problem while attempting to acess
a property or method. The prob may be: a reference is missing (see Microsoft
Knowledge Base article 283806) / an Expression is misspelled / A user-defined
funtion is delared as a sub or private funtion in a module / Security in
Access is set to Med or High & Microsoft Jet 4.0 SP8 update is not installed.


Please note: I work for a very large company, and 3 separate IT people
have tried re-installing the programs. They assure me there is not a problem
with our copies of Access, and that all updates have been applied. Also...
security is set to minimum, and the same errors occur whether the database is
blank/just created (in file type2002/3) or we open up an older 2000
database--no more coding (VBA, queries etc) has been added.

Any suggestions, other than staying with 2000. Thank you sooo much for your
time & help!! ~Richard

 

[Douglas J Steele]

Take a look at http://www.accessmvp.com/djsteele/AccessReferenceErrors.html
to see how to resolve References problems.

 

[Richard R3]

What code modules should I look at? I get the same error code in V2003 on a
blank database--a database I just created, that has no other object than the
text file, or Excel worksheet, I am trying to import.

Thanks again ~R

Take a look at http://www.accessmvp.com/djsteele/AccessReferenceErrors.html
to see how to resolve References problems.

--
Doug Steele, Microsoft Access MVP

(no e-mails, please!)

I am having trouble importing data @ work, and the problem seems to depend on
the version of Access I use. The troubles are the same, no matter if the
database is new/blank, or if it is an older database already having been
created & used by others. The problem seems to be isolated to the task of
changing field types during the import proccess--when I click each
column/field.

V2000 imports fine, and allows the changing of field types--but we would
like to update to V2003, as we have a new project coming up which we hope
will have all the new functionality & coding.

V2000 allows import but only allows the changing of field type for the first
field/column. When I select the other fields, the data type does not change
from what was selected for the first column--when you change the type, you
can see the first column is still the only one being changed.

V2003 is "broken". When I select the second column during the import
process, I get an error. It says, "There was an error loading an ActiveX
control on one of your forms or reports...The expression may not result in
the name of a macro, the name of a user-defined function, or [Event
Procedure]...There may have been an error evaluating the funtion, event, or
macro...{under more help--VBA encountered a problem while attempting to acess
a property or method. The prob may be: a reference is missing (see Microsoft
Knowledge Base article 283806) / an Expression is misspelled / A user-defined
funtion is delared as a sub or private funtion in a module / Security in
Access is set to Med or High & Microsoft Jet 4.0 SP8 update is not installed.


Please note: I work for a very large company, and 3 separate IT people
have tried re-installing the programs. They assure me there is not a problem
with our copies of Access, and that all updates have been applied. Also...
security is set to minimum, and the same errors occur whether the database is
blank/just created (in file type2002/3) or we open up an older 2000
database--no more coding (VBA, queries etc) has been added.

Any suggestions, other than staying with 2000. Thank you sooo much for your
time & help!! ~Richard

 

[Jerry Whittle]

It could be that your ACCWIZ.DLL file is incorrect or not properly
registered. There's plenty of ways that this can happen including installing
A03 first then trying to install an older version of Access. If running
multiple copies of Access programs, always install the oldest first and the
newest last.
Check out:

http://support.microsoft.com/default.aspx?scid=kb;en-us;835519

Even though it talks about linked tables, the same remedy fixed a similar
problem as your's for me.

--
Jerry Whittle
Light. Strong. Cheap. Pick two. Keith Bontrager - Bicycle Builder.

I am having trouble importing data @ work, and the problem seems to depend on
the version of Access I use. The troubles are the same, no matter if the
database is new/blank, or if it is an older database already having been
created & used by others. The problem seems to be isolated to the task of
changing field types during the import proccess--when I click each
column/field.

V2000 imports fine, and allows the changing of field types--but we would
like to update to V2003, as we have a new project coming up which we hope
will have all the new functionality & coding.

V2000 allows import but only allows the changing of field type for the first
field/column. When I select the other fields, the data type does not change
from what was selected for the first column--when you change the type, you
can see the first column is still the only one being changed.

V2003 is "broken". When I select the second column during the import
process, I get an error. It says, "There was an error loading an ActiveX
control on one of your forms or reports...The expression may not result in
the name of a macro, the name of a user-defined function, or [Event
Procedure]...There may have been an error evaluating the funtion, event, or
macro...{under more help--VBA encountered a problem while attempting to acess
a property or method. The prob may be: a reference is missing (see Microsoft
Knowledge Base article 283806) / an Expression is misspelled / A user-defined
funtion is delared as a sub or private funtion in a module / Security in
Access is set to Med or High & Microsoft Jet 4.0 SP8 update is not installed.


Please note: I work for a very large company, and 3 separate IT people
have tried re-installing the programs. They assure me there is not a problem
with our copies of Access, and that all updates have been applied. Also...
security is set to minimum, and the same errors occur whether the database is
blank/just created (in file type2002/3) or we open up an older 2000
database--no more coding (VBA, queries etc) has been added.

Any suggestions, other than staying with 2000. Thank you sooo much for your
time & help!! ~Richard

 

[Douglas J Steele]

You don't need to look at any specific modules. You look under Tools |
References from the menu bar when you're in the VB Editor.

--
Doug Steele, Microsoft Access MVP

(no e-mails, please!)

What code modules should I look at? I get the same error code in V2003 on a
blank database--a database I just created, that has no other object than the
text file, or Excel worksheet, I am trying to import.

Thanks again ~R

Take a look at http://www.accessmvp.com/djsteele/AccessReferenceErrors.html
to see how to resolve References problems.

--
Doug Steele, Microsoft Access MVP

(no e-mails, please!)

I am having trouble importing data @ work, and the problem seems to

depend
on

the version of Access I use. The troubles are the same, no matter if the
database is new/blank, or if it is an older database already having been
created & used by others. The problem seems to be isolated to the task of
changing field types during the import proccess--when I click each
column/field.

V2000 imports fine, and allows the changing of field types--but we would
like to update to V2003, as we have a new project coming up which we hope
will have all the new functionality & coding.

V2000 allows import but only allows the changing of field type for the first
field/column. When I select the other fields, the data type does not change
from what was selected for the first column--when you change the type, you
can see the first column is still the only one being changed.

V2003 is "broken". When I select the second column during the import
process, I get an error. It says, "There was an error loading an ActiveX
control on one of your forms or reports...The expression may not result in
the name of a macro, the name of a user-defined function, or [Event
Procedure]...There may have been an error evaluating the funtion,

event,
or

macro...{under more help--VBA encountered a problem while attempting

to
acess

a property or method. The prob may be: a reference is missing (see Microsoft
Knowledge Base article 283806) / an Expression is misspelled / A user-defined
funtion is delared as a sub or private funtion in a module / Security in
Access is set to Med or High & Microsoft Jet 4.0 SP8 update is not installed.


Please note: I work for a very large company, and 3 separate IT people
have tried re-installing the programs. They assure me there is not a problem
with our copies of Access, and that all updates have been applied. Also...
security is set to minimum, and the same errors occur whether the

database
is

blank/just created (in file type2002/3) or we open up an older 2000
database--no more coding (VBA, queries etc) has been added.

Any suggestions, other than staying with 2000. Thank you sooo much

for
your

time & help!! ~Richard