Hi Lynda.

>Doug, I'm sorry to bother you again but this problem with AccPac data just won't go away and I don't know anyone else in the VFP community who even understands what AccPac is...

No problem. However, there are lots of folks around here who know a lot more about ACCPAC than I do.

>On some workstations, including mine when run on my own network, a form which needs data from AccPac's Arcust file displays a GetFile() dialog for help in locating the Arcust file. The Prodata database is open (although not current), the Arcust file has been Used, a view of Arcust from the application database has been added to the form's DE -- all to no avail.

Since the actual name of the table is ARCUSTnn.DBF, where nn is the company number, is it possible that the form is expecting to talk to an alias of ARCUST but the table is open using its "natural" alias of ARCUSTnn? Or perhaps it's the other way around -- ARCUSTnn was opened with an alias of ARCUST but the form is expecting ARCUSTnn.

>It seems to be simply the contrariness of AccPac.

ACCPAC data isn't any more contrary than any other DBC, with the exception that the tables are named TABLEnn.DBF.

Doug