By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
434,572 Members | 963 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 434,572 IT Pros & Developers. It's quick & easy.

Run-time error 3075 only for one user

P: n/a
jr
Hello everyone! I am new to this sort of postings so I'm not even
sure
if this is the correct place to start. Anyway, I would realy
appreciate any help. I have a some VBA code that works quite happily
in a number of machines and for different users. Recently we had to
open a new account for a user in one of the machines and when the
code
runs it shows a run-time error '3075'. Nonetheless if I switch users
in the same machine and run the code there are no problems at all. Is
there any sort of settings that would be different in the newly
created account?
Thanks in advance,

Feb 15 '07 #1
Share this Question
Share on Google+
2 Replies


P: n/a
Hi, JR.
I have a some VBA code that works quite happily
in a number of machines and for different users.
Hmm. Too vague.
Recently we had to
open a new account for a user in one of the machines and when the
code
runs it shows a run-time error '3075'.
Let's take a look at that error number in the Immediate Window:

?error(3075)
Application-defined or object-defined error

Hmm. Vague. The Access developer's code is using an application-defined or
a user-defined object inappropriately in some way.
Is
there any sort of settings that would be different in the newly
created account?
Depends upon permissions, installation choices, workstation configuration
(including OS version, Access version, Jet version, MDAC version, and all
the service packs), network configuration, Windows group policies, and/or
user preferences. Sorry, but I can't get any more precise than that due to
your unwillingness to reveal any useful information about your problem.

HTH.
Gunny

See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips and tutorials.
Blog: http://DataDevilDog.BlogSpot.com
http://www.Access.QBuilt.com/html/ex...ributors2.html for contact
info.
"jr" <j.*****@gmail.comwrote in message
news:11*********************@h3g2000cwc.googlegrou ps.com...
Hello everyone! I am new to this sort of postings so I'm not even
sure
if this is the correct place to start. Anyway, I would realy
appreciate any help. I have a some VBA code that works quite happily
in a number of machines and for different users. Recently we had to
open a new account for a user in one of the machines and when the
code
runs it shows a run-time error '3075'. Nonetheless if I switch users
in the same machine and run the code there are no problems at all. Is
there any sort of settings that would be different in the newly
created account?
Thanks in advance,

Feb 15 '07 #2

P: n/a
jr
Hi again! OK, the Excek VBA macro connects to a database in access and
queries a table to write a report. If I run it from the account of say
user "user1" there are no problems at all. Then I switch to user
"user2" and run the macro, things go well until it arrives to the
following statement:
"select distinct dealer,target,qsl,msl,drawdown,fx_delta,capital " _
& "from 03_capital a " _
& "where a.effective = (select max(c.effective) from
03_capital c where c.dealer=a.dealer) " _
& "and isnull(strategy) and not dealer in ('DTG') " _
& "and a.dealer in " & dealer_string

My guess if that the 3075 error is triggered by the use of the
apostrophed in 'DTG'. Nonetheless, I can't undertand why I would work
for every other user except for "user2". That's why I was asking if
there are any settings that would have to be adjusted. I apologise for
the vagueness, but as you yourself suggested '69 Camaro, the error
description is not too helpful either...

JR


On Feb 15, 9:03 pm, "'69 Camaro" <ForwardZERO_SPAM.To.
69Cam...@Spameater.orgZERO_SPAMwrote:
Hi, JR.
I have a some VBA code that works quite happily
in a number of machines and for different users.

Hmm. Too vague.
Recently we had to
open a new account for a user in one of the machines and when the
code
runs it shows a run-time error '3075'.

Let's take a look at that error number in the Immediate Window:

?error(3075)
Application-defined or object-defined error

Hmm. Vague. The Access developer's code is using an application-defined or
a user-defined object inappropriately in some way.
Is
there any sort of settings that would be different in the newly
created account?

Depends upon permissions, installation choices, workstation configuration
(including OS version, Access version, Jet version, MDAC version, and all
the service packs), network configuration, Windows group policies, and/or
user preferences. Sorry, but I can't get any more precise than that due to
your unwillingness to reveal any useful information about your problem.

HTH.
Gunny

Seehttp://www.QBuilt.comfor all your database needs.
Seehttp://www.Access.QBuilt.comfor Microsoft Access tips and tutorials.
Blog: http://DataDevilDog.BlogSpot.comhttp...utors2.htmlfor contact
info.
Feb 19 '07 #3

This discussion thread is closed

Replies have been disabled for this discussion.