Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Programmer won't support - app works on one machine but not next...

Status
Not open for further replies.

hmunster

Technical User
Jul 16, 2001
13
US
This app, which I didn't develop, has a form which pulls data from a table with a key field, nothing unusual. But... on some computers it simply doesn't get the data from the table - the window on the form is just empty although I know there are records in the table. The app is a runtime using Access 2002. I don't have access to the design, and the programmer has made himself unavailable. I've tried updating MDAC and Jet to the latest, reinstalling the app after each revision, no help. On some machines, whether Windows 95, 98 or 2K pro, it works just fine - I'm copying the same database (MDE) from working machine to non-working machine, so I know the data is there. What else should I try? Thank you!
 
Windows 95 doesn't support OfficeXP or Access2002 so if the machine you're trying to run it on is Win95 it won't work. Aside to that, sounds like the computer might not have access to the backend db holding the data (if there is one, usually there is with MDE's). Check that the user has rights to the directory with the backend file.

Joe Miller
joe.miller@flotech.net
 
Perhaps the programmer used a mapping (F:)to the drive where the linked table is in lieu of UNC (\\Server\Directory.)

Make sure all machines have the same mapping ?



 
Hire a new programmer. I'm available, and I support whatever the paying customer wants and is legal. Other than that, I suspect that the MDE program is "accessing" a seperate file (".MDB") which is not available to the machines where it doesn't run. If the system / app operates on SOME other machines, but not all, then the data (".MDB") is probably on a shared network drive, and it is probably "MAPPED" on the machines where it does work and either not mapped or maped differently on the machines where it does work.

Even if you wont hire me, I STILL suggest you terminate the (*nbiou7**HBo*&BN8OP7, who refuses to cooperate with your needs. I would also suggest that before you fire him, have your legal rep draw up a suit aginst him, with severe consequences for refusal to provide the complete source code for the ".MDE" program. Show him the suit during the terminiation interview.

MichaelRed
mred@att.net

There is never time to do it right but there is always time to do it over
 
No, can't be either of those problems. The app has multiple tables and it does pull data from most of them - it's one table in particular that is giving the problem, all tables are in the same MDE. We're thinking Active-X or MDAC, but I've applied the same MDAC 2.6 (and Jet 4) on every machine but the problem remains on some but not others. The programmer just called and is sending the source MDB. I dunno what I'm gonna do with it, but...
 
I re-itterate my suggestions and offer.

MichaelRed
mred@att.net

There is never time to do it right but there is always time to do it over
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top