.adp project not working internationally

  • Thread starter Thread starter T. Bernard
  • Start date Start date
T

T. Bernard

I have created an .adp project that works just fine for
me. I am just testing on a simple continous form, that
has its data source as a View. I have "SA" rights on the
server so I have no issues.

We then tested out the user rights, by creating a user
group on the SQL server, and assigning users to the user
group. We got another user located here in Kanas City
(this is where I am located) set up with their user group,
and the .adp project works just fine for them.

We then set-up a London User with the same rights, and the
database will not pull in any of the SQL components. The
tables, views and stored procs do not show in the database
window. We ran a trace, and it shows that the user
connects to the database, but nothing occurs after that.
We created an ODBC connection for the user to the same SQL
server, and this appears to work just fine. We opened up
the .adp project, went to File -> Connection, and it
showed the correct Server/Database, we then clicked "Test
Connection" and it said the connection was succesful. We
also had the user "ping" the SQL server, and that was
successful as well.

I am thinking there is something wrong on the .adp side,
but I am not sure. Is there a seperate version of MS
Access for European settings that does not support .adp
projects? Maybe there is something within the .adp
project I must set up differently for our international
users.

If anyone has run into this problem, or has any
advice/ideas on how to resolve this it will be greatly
appreciated.

Thank you for your time.

T.J.
 
TB> If anyone has run into this problem, or has any
TB> advice/ideas on how to resolve this it will be
TB> greatly appreciated.

Didn't run into this problem, but I would check the language settings on the
London machine, and if they are different from the U.S. machine, would try
setting them to the same as in U.S.

Vadim
 
Seems more like a versioning problem (Access 2000 versus 2002 versus 2003;
VBA 5.1,5.5, 56; MDAC 2.1, 2.5, 2.7; etc.) than an internationalizing
problem to me.

Personnally, I have used the french and english version of Access against
french and english versions of SQL Server, all with different regionals
settings, without any problem.

You should try the /decompile option at the London User site and make sure
that the proper version of MDAC is installed.

S. L.
 
Also, the configuration settings for a firewall, a proxy or use a VPN can be
tricky sometime. Make sure that's not the case here.

S. L.
 
Back
Top