Txt File Import Different on Different Machines

syoung7903

Registered User.
Local time
Today, 22:02
Joined
Jan 1, 2001
Messages
18
I have tested my database on three machines:

Machine 1:
Access 2003 Version 11.5614
References checked: VB for applications, M A 11.0 Object Library, Ole Automation, M DAO 3.6 Object Library, M ActiveX Data Object 2.1 Library.

Machine 2:
Access 2000 Version 9.0.4402 SR-1
References checked: all the same EXCEPT M A 9.0 Object Library instead of 11.0 Library.

Machine 3:
Exact same version and references as Machine 2.

I have a Macro that imports a text file (TransferText...fixed width with a defined import specification).

The import works perfect on Machines 1 and 2 but the specifications don't work correctly on Machine 3.

Any ideas on where I should investigate to see why this difference?

Thanks all!
Suzanne

P.S. I haven't a clue what References are. I just noticed when researching my problem on this forum and others that when References were different it was a problem. Also, none of my References show Missing.
 
In what way does the data differ on the machines?


Fuga.
 
References are Microsoft's attempt to allow you implement a feature called "late binding" on library files.

Basically, your .DLL, .OCX, and other executable libraries contain code modules or data that your program might need. The reference is the thing that makes Windows look for those modules at program load time. The Windows image loader can use this information to dynamically build links to the library files (which is why DLL means Dynamic Link Libraries).

I won't go into the hardware - it is confusing on a good day 'cause the Intel processor ain't one of the more elegant CPU chips of the world. (The old Apple chip, a Motorola 68xx or 68xxx series, was far better, architecturally speaking.) But anyway, the image loader does what it needs to do to make the program work with the listed libraries in the reference list.

NOW, as to why machine 2 works and machine 3 doesn't....

Was Access installed using the same methods and options on both machines? For instance, a "Typical" install and a "Custom" install won't always do the same thing and yet MIGHT result in the same references. But if you left something out - like the ImportText wizard - in one of them and not in the other, that might account for the difference. I'm not saying that the ImportText wizard is what you are missing. It was meant as an example of something you COULD be missing.
 

Users who are viewing this thread

Back
Top Bottom