Skip to main content

Windows 7 - Access 2010

  • March 4, 2011
  • 3 replies
  • 0 views

[Migrated content. Thread originally posted on 03 March 2011]

I have a version 7.2 program that loads a line sequential file into a table in an Access database. It works fine on Windows XP and Access 2007. It does not work on Windows 7 and Access 2010. How can I generate a msado.def file that will work on the new platform? Thanks!

3 replies

[Migrated content. Thread originally posted on 03 March 2011]

I have a version 7.2 program that loads a line sequential file into a table in an Access database. It works fine on Windows XP and Access 2007. It does not work on Windows 7 and Access 2010. How can I generate a msado.def file that will work on the new platform? Thanks!
Primary quuestion is whether the msado activex object is installed on the machine. If it is not, then install it.

If it is, another question is whether this is a 64 or 32 bit OS. If the former, you have to ensure that the activex is matching the runtime in the question of 32 or 64.

There are no limits to the runtimes ability to host activex on Win7 compared to former OS's.

[Migrated content. Thread originally posted on 03 March 2011]

I have a version 7.2 program that loads a line sequential file into a table in an Access database. It works fine on Windows XP and Access 2007. It does not work on Windows 7 and Access 2010. How can I generate a msado.def file that will work on the new platform? Thanks!
Primary quuestion is whether the msado activex object is installed on the machine. If it is not, then install it.

If it is, another question is whether this is a 64 or 32 bit OS. If the former, you have to ensure that the activex is matching the runtime in the question of 32 or 64.

There are no limits to the runtimes ability to host activex on Win7 compared to former OS's.

[Migrated content. Thread originally posted on 03 March 2011]

I have a version 7.2 program that loads a line sequential file into a table in an Access database. It works fine on Windows XP and Access 2007. It does not work on Windows 7 and Access 2010. How can I generate a msado.def file that will work on the new platform? Thanks!
Primary quuestion is whether the msado activex object is installed on the machine. If it is not, then install it.

If it is, another question is whether this is a 64 or 32 bit OS. If the former, you have to ensure that the activex is matching the runtime in the question of 32 or 64.

There are no limits to the runtimes ability to host activex on Win7 compared to former OS's.