Why Would A Dlookup Function Work On One Computer But Not On Another Computer? [WiredBox.Net - Office Newsgroups]

Group: Microsoft Access » microsoft.public.access.forms
Thread: Why Would A Dlookup Function Work On One Computer But Not On Another Computer?

Why Would A Dlookup Function Work On One Computer But Not On Another Computer?

R Tanner <nouveauricheinvestments[ at ]gmail.com> 12/22/2008 4:33:28 PM

I have a main form with a dlookup function that looks up an account
number based on another textbox that is looking up the oldest record
in my table. This is all fine and dandy and works wonderfully on most
of my users' computers, but there are a couple people whom my dlookup
function returns a null error. I don't get it, because I know there
are records there. There IS an account number there in the table for
this record, and it works fine on every computer except two...What
could cause this?

Re: Why Would A Dlookup Function Work On One Computer But Not On Another Computer?

"Jeff Boyce" <nonsense[ at ]nonsense.com> 12/22/2008 4:53:43 PM

?Perhaps the field being DLookedUp has a null value, even though a record
exists?

Regards

Jeff Boyce
Microsoft Office/Access MVP

"R Tanner" <nouveauricheinvestments[ at ]gmail.com> wrote in message
news:2f31542a-e207-4c92-a85c-62d259c92981[ at ]l38g2000vba.googlegroups.com...
[Quoted Text]
>I have a main form with a dlookup function that looks up an account
> number based on another textbox that is looking up the oldest record
> in my table. This is all fine and dandy and works wonderfully on most
> of my users' computers, but there are a couple people whom my dlookup
> function returns a null error. I don't get it, because I know there
> are records there. There IS an account number there in the table for
> this record, and it works fine on every computer except two...What
> could cause this?

Re: Why Would A Dlookup Function Work On One Computer But Not On Another Computer?

R Tanner <nouveauricheinvestments[ at ]gmail.com> 12/22/2008 5:05:19 PM

On Dec 22, 9:53 am, "Jeff Boyce" <nonse...[ at ]nonsense.com> wrote:
[Quoted Text]
> ?Perhaps the field being DLookedUp has a null value, even though a record
> exists?
>
> Regards
>
> Jeff Boyce
> Microsoft Office/Access MVP
>
> "R Tanner" <nouveauricheinvestme...[ at ]gmail.com> wrote in message
>
> news:2f31542a-e207-4c92-a85c-62d259c92981[ at ]l38g2000vba.googlegroups.com...
>
> >I have a main form with a dlookup function that looks up an account
> > number based on another textbox that is looking up the oldest record
> > in my table. This is all fine and dandy and works wonderfully on most
> > of my users' computers, but there are a couple people whom my dlookup
> > function returns a null error. I don't get it, because I know there
> > are records there. There IS an account number there in the table for
> > this record, and it works fine on every computer except two...What
> > could cause this?

Nope. The field I am looking up is not null. The dlookup function
works fine on my computer, as well as most of the users' computers.
There are a few computers it does not work on though. This is my
code, so you know what's happening:

Public Function CheckForOverDueTickets()

Dim MyForm As Form
Set MyForm = Forms![frmSplash]

Dim ComplaintHours As Long, MyCompDate As Date, MyCompAccount As Long,
TradeHours As Long, TradeDate As Date, TradeAccount As Long

On Error GoTo NoComplaint
MyCompDate = DMin("[StartTime]", "[ComplaintTickets]",
"[ComplaintTickets].StatusID=2")

ComplaintHours = DateDiff("h", MyCompDate, Now)

Forms![frmSplash]![CompDate] = MyCompDate
Forms![frmSplash]![CompDif] = ComplaintHours & " Hours Unresolved"

MyCompAccount = DLookup("[Account]", "[ComplaintTickets]",
"ComplaintTickets.StartTime=Forms![frmSplash]![CompDate]")
Forms![frmSplash]![CompAccount] = MyCompAccount

GoTo TryTrades

NoComplaint:

MyForm![CompLabel].Visible = True
MyForm![CompDate].Visible = False
MyForm![CompAccount].Visible = False
MyForm![CompDif].Visible = False
MyForm![NoComplaints].Visible = True

TryTrades:

On Error GoTo NoTrade
TradeDate = DMin("DAT", "[Pending Tickets]", "[Pending
Tickets].Status=2")
TradeHours = DateDiff("h", TradeDate, Now)
Forms![frmSplash]![TradeDate] = TradeDate
Forms![frmSplash]![TradeDiff] = TradeHours & " Hours Unresolved"
TradeAccount = DLookup("[Account]", "[Pending Tickets]", "[Pending
Tickets].DAT=Forms![frmSplash]![TradeDate]")
Forms![frmSplash]![TradeAccount] = TradeAccount

Exit Function

NoTrade:
MyForm![TradeLabel].Visible = True
MyForm![TradeDate].Visible = False
MyForm![TradeAccount].Visible = False
MyForm![TradeDiff].Visible = False
MyForm![NoTrades].Visible = True

End Function

On my computer as well as most other computers, this works fine. On a
select few computers (2 to be exact), the dlookup function for the
account number throws a null error. I have went back into the
database and looked up the record with the date which is returned by :
MyCompDate = DMin("[StartTime]", "[ComplaintTickets]",
"[ComplaintTickets].StatusID=2") and there are no problems with it.
There is an account number there.

Re: Why Would A Dlookup Function Work On One Computer But Not On Another Computer?

"Douglas J. Steele" <NOSPAM_djsteele[ at ]NOSPAM_gmail.com> 12/22/2008 8:44:54 PM

Try:

MyCompAccount = DLookup("[Account]", "[ComplaintTickets]", _
"StartTime=" & Format(Forms![frmSplash]![CompDate], "\yyyy\-mm\-dd\#"))

TradeAccount = DLookup("[Account]", "[Pending Tickets]", _
"DAT=" & Format(Forms![frmSplash]![TradeDate], "\yyyy\-mm\-dd\#"))

No idea why it would work on some machines but not on others though.

--
Doug Steele, Microsoft Access MVP
http://I.Am/DougSteele
(no private e-mails, please)

"R Tanner" <nouveauricheinvestments[ at ]gmail.com> wrote in message
news:c200b03a-e2e8-4390-9f73-d345fc9b1d0c[ at ]g1g2000pra.googlegroups.com...
[Quoted Text]
> On Dec 22, 9:53 am, "Jeff Boyce" <nonse...[ at ]nonsense.com> wrote:
>> ?Perhaps the field being DLookedUp has a null value, even though a record
>> exists?
>>
>> Regards
>>
>> Jeff Boyce
>> Microsoft Office/Access MVP
>>
>> "R Tanner" <nouveauricheinvestme...[ at ]gmail.com> wrote in message
>>
>> news:2f31542a-e207-4c92-a85c-62d259c92981[ at ]l38g2000vba.googlegroups.com...
>>
>> >I have a main form with a dlookup function that looks up an account
>> > number based on another textbox that is looking up the oldest record
>> > in my table. This is all fine and dandy and works wonderfully on most
>> > of my users' computers, but there are a couple people whom my dlookup
>> > function returns a null error. I don't get it, because I know there
>> > are records there. There IS an account number there in the table for
>> > this record, and it works fine on every computer except two...What
>> > could cause this?
>
> Nope. The field I am looking up is not null. The dlookup function
> works fine on my computer, as well as most of the users' computers.
> There are a few computers it does not work on though. This is my
> code, so you know what's happening:
>
> Public Function CheckForOverDueTickets()
>
> Dim MyForm As Form
> Set MyForm = Forms![frmSplash]
>
> Dim ComplaintHours As Long, MyCompDate As Date, MyCompAccount As Long,
> TradeHours As Long, TradeDate As Date, TradeAccount As Long
>
>
>
> On Error GoTo NoComplaint
> MyCompDate = DMin("[StartTime]", "[ComplaintTickets]",
> "[ComplaintTickets].StatusID=2")
>
> ComplaintHours = DateDiff("h", MyCompDate, Now)
>
> Forms![frmSplash]![CompDate] = MyCompDate
> Forms![frmSplash]![CompDif] = ComplaintHours & " Hours Unresolved"
>
> MyCompAccount = DLookup("[Account]", "[ComplaintTickets]",
> "ComplaintTickets.StartTime=Forms![frmSplash]![CompDate]")
> Forms![frmSplash]![CompAccount] = MyCompAccount
>
> GoTo TryTrades
>
> NoComplaint:
>
> MyForm![CompLabel].Visible = True
> MyForm![CompDate].Visible = False
> MyForm![CompAccount].Visible = False
> MyForm![CompDif].Visible = False
> MyForm![NoComplaints].Visible = True
>
> TryTrades:
>
> On Error GoTo NoTrade
> TradeDate = DMin("DAT", "[Pending Tickets]", "[Pending
> Tickets].Status=2")
> TradeHours = DateDiff("h", TradeDate, Now)
> Forms![frmSplash]![TradeDate] = TradeDate
> Forms![frmSplash]![TradeDiff] = TradeHours & " Hours Unresolved"
> TradeAccount = DLookup("[Account]", "[Pending Tickets]", "[Pending
> Tickets].DAT=Forms![frmSplash]![TradeDate]")
> Forms![frmSplash]![TradeAccount] = TradeAccount
>
> Exit Function
>
>
> NoTrade:
> MyForm![TradeLabel].Visible = True
> MyForm![TradeDate].Visible = False
> MyForm![TradeAccount].Visible = False
> MyForm![TradeDiff].Visible = False
> MyForm![NoTrades].Visible = True
>
>
>
>
> End Function
>
>
> On my computer as well as most other computers, this works fine. On a
> select few computers (2 to be exact), the dlookup function for the
> account number throws a null error. I have went back into the
> database and looked up the record with the date which is returned by :
> MyCompDate = DMin("[StartTime]", "[ComplaintTickets]",
> "[ComplaintTickets].StatusID=2") and there are no problems with it.
> There is an account number there.

Re: Why Would A Dlookup Function Work On One Computer But Not On Another Computer?

R Tanner <nouveauricheinvestments[ at ]gmail.com> 12/31/2008 7:20:49 PM

On Dec 22, 1:44 pm, "Douglas J. Steele"
<NOSPAM_djsteele[ at ]NOSPAM_gmail.com> wrote:
[Quoted Text]
> Try:
>
> MyCompAccount = DLookup("[Account]", "[ComplaintTickets]", _
> "StartTime=" & Format(Forms![frmSplash]![CompDate], "\yyyy\-mm\-dd\#"))
>
> TradeAccount = DLookup("[Account]", "[Pending Tickets]", _
> "DAT=" & Format(Forms![frmSplash]![TradeDate], "\yyyy\-mm\-dd\#"))
>
> No idea why it would work on some machines but not on others though.
>
> --
> Doug Steele, Microsoft Access MVPhttp://I.Am/DougSteele
> (no private e-mails, please)
>
> "R Tanner" <nouveauricheinvestme...[ at ]gmail.com> wrote in message
>
> news:c200b03a-e2e8-4390-9f73-d345fc9b1d0c[ at ]g1g2000pra.googlegroups.com...
>
>
>
> > On Dec 22, 9:53 am, "Jeff Boyce" <nonse...[ at ]nonsense.com> wrote:
> >> ?Perhaps the field being DLookedUp has a null value, even though a record
> >> exists?
>
> >> Regards
>
> >> Jeff Boyce
> >> Microsoft Office/Access MVP
>
> >> "R Tanner" <nouveauricheinvestme...[ at ]gmail.com> wrote in message
>
> >>news:2f31542a-e207-4c92-a85c-62d259c92981[ at ]l38g2000vba.googlegroups.com....
>
> >> >I have a main form with a dlookup function that looks up an account
> >> > number based on another textbox that is looking up the oldest record
> >> > in my table. This is all fine and dandy and works wonderfully on most
> >> > of my users' computers, but there are a couple people whom my dlookup
> >> > function returns a null error. I don't get it, because I know there
> >> > are records there. There IS an account number there in the table for
> >> > this record, and it works fine on every computer except two...What
> >> > could cause this?
>
> > Nope. The field I am looking up is not null. The dlookup function
> > works fine on my computer, as well as most of the users' computers.
> > There are a few computers it does not work on though. This is my
> > code, so you know what's happening:
>
> > Public Function CheckForOverDueTickets()
>
> > Dim MyForm As Form
> > Set MyForm = Forms![frmSplash]
>
> > Dim ComplaintHours As Long, MyCompDate As Date, MyCompAccount As Long,
> > TradeHours As Long, TradeDate As Date, TradeAccount As Long
>
> > On Error GoTo NoComplaint
> > MyCompDate = DMin("[StartTime]", "[ComplaintTickets]",
> > "[ComplaintTickets].StatusID=2")
>
> > ComplaintHours = DateDiff("h", MyCompDate, Now)
>
> > Forms![frmSplash]![CompDate] = MyCompDate
> > Forms![frmSplash]![CompDif] = ComplaintHours & " Hours Unresolved"
>
> > MyCompAccount = DLookup("[Account]", "[ComplaintTickets]",
> > "ComplaintTickets.StartTime=Forms![frmSplash]![CompDate]")
> > Forms![frmSplash]![CompAccount] = MyCompAccount
>
> > GoTo TryTrades
>
> > NoComplaint:
>
> > MyForm![CompLabel].Visible = True
> > MyForm![CompDate].Visible = False
> > MyForm![CompAccount].Visible = False
> > MyForm![CompDif].Visible = False
> > MyForm![NoComplaints].Visible = True
>
> > TryTrades:
>
> > On Error GoTo NoTrade
> > TradeDate = DMin("DAT", "[Pending Tickets]", "[Pending
> > Tickets].Status=2")
> > TradeHours = DateDiff("h", TradeDate, Now)
> > Forms![frmSplash]![TradeDate] = TradeDate
> > Forms![frmSplash]![TradeDiff] = TradeHours & " Hours Unresolved"
> > TradeAccount = DLookup("[Account]", "[Pending Tickets]", "[Pending
> > Tickets].DAT=Forms![frmSplash]![TradeDate]")
> > Forms![frmSplash]![TradeAccount] = TradeAccount
>
> > Exit Function
>
> > NoTrade:
> > MyForm![TradeLabel].Visible = True
> > MyForm![TradeDate].Visible = False
> > MyForm![TradeAccount].Visible = False
> > MyForm![TradeDiff].Visible = False
> > MyForm![NoTrades].Visible = True
>
> > End Function
>
> > On my computer as well as most other computers, this works fine. On a
> > select few computers (2 to be exact), the dlookup function for the
> > account number throws a null error. I have went back into the
> > database and looked up the record with the date which is returned by :
> > MyCompDate = DMin("[StartTime]", "[ComplaintTickets]",
> > "[ComplaintTickets].StatusID=2") and there are no problems with it.
> > There is an account number there.- Hide quoted text -
>
> - Show quoted text -

I am getting the following error for this for ONLY 2 of the
application users:

Error Number: 94
Error Description: Invalid Use Of Null
Error Source: Trade Tickets

I am clueless...It doesn't work for the two people it really matters
for...Any insight would really be appreciated...I'm not sure what I
can do differently with this function...I hate to rewrite it since it
works perfectly...It has to be something small...

Re: Why Would A Dlookup Function Work On One Computer But Not On Another Computer?

"tkelley via AccessMonster.com" <u47368[ at ]uwe> 12/31/2008 8:32:39 PM

Is this all a local database, run on each user's local machine?

Is it located on a shared drive? If so, the user's in question have rights
to the folder?

Is it a SQL backend? If so, the user's in question have SELECT rights?

Just a couple of thoughts. I've learned to not always take an Access error
at it's word, and look beyond what it seems to obviously be saying when I
find weird things like this.

R Tanner wrote:
[Quoted Text]
>On Dec 22, 1:44Â pm, "Douglas J. Steele"
><NOSPAM_djsteele[ at ]NOSPAM_gmail.com> wrote:
>> Try:
>>
>[quoted text clipped - 99 lines]
>>
>> - Show quoted text -
>
>I am getting the following error for this for ONLY 2 of the
>application users:
>
>Error Number: 94
>Error Description: Invalid Use Of Null
>Error Source: Trade Tickets
>
>I am clueless...It doesn't work for the two people it really matters
>for...Any insight would really be appreciated...I'm not sure what I
>can do differently with this function...I hate to rewrite it since it
>works perfectly...It has to be something small...

--
Message posted via AccessMonster.com
http://www.accessmonster.com/Uwe/Forums.aspx/access-forms/200812/1

Re: Why Would A Dlookup Function Work On One Computer But Not On Another Computer?

R Tanner <tanner.robin[ at ]gmail.com> 12/31/2008 8:54:08 PM

On Dec 31, 1:32 pm, "tkelley via AccessMonster.com" <u47368[ at ]uwe>
wrote:
[Quoted Text]
> Is this all a local database, run on each user's local machine?
>
> Is it located on a shared drive? If so, the user's in question have rights
> to the folder?
>
> Is it a SQL backend? If so, the user's in question have SELECT rights?
>
> Just a couple of thoughts. I've learned to not always take an Access error
> at it's word, and look beyond what it seems to obviously be saying when I
> find weird things like this.
>
>
>
> R Tanner wrote:
> >On Dec 22, 1:44 pm, "Douglas J. Steele"
> ><NOSPAM_djsteele[ at ]NOSPAM_gmail.com> wrote:
> >> Try:
>
> >[quoted text clipped - 99 lines]
>
> >> - Show quoted text -
>
> >I am getting the following error for this for ONLY 2 of the
> >application users:
>
> >Error Number: 94
> >Error Description: Invalid Use Of Null
> >Error Source: Trade Tickets
>
> >I am clueless...It doesn't work for the two people it really matters
> >for...Any insight would really be appreciated...I'm not sure what I
> >can do differently with this function...I hate to rewrite it since it
> >works perfectly...It has to be something small...
>
> --
> Message posted via AccessMonster.comhttp://www.accessmonster.com/Uwe/Forums.aspx/access-forms/200812/1

Yes, it is a local access database on a shared network drive. Yes,
the users have rights to the folder. It is weird because the one user
who is having problems is the senior manager and the other is the
senior trade specialist. This [seems to be] the only problem these
two users are having with the application.

Re: Why Would A Dlookup Function Work On One Computer But Not On Another Computer?

"tkelley via AccessMonster.com" <u47368[ at ]uwe> 12/31/2008 9:02:20 PM

Is it FE/BE with table links? If so, you're sure the users in question have
the most current link? (If you had added a field referenced in the criteria
of the DLookup, and they don't have current links ...)

Are they power-users? Have they been dinking around in the design where they
shouldn't have been? You've tried a fresh, new copy of the database on their
machine that is an EXACT copy of the one that works on yours?

Just throwing more stuff out there ...

R Tanner wrote:
[Quoted Text]
>On Dec 31, 1:32 pm, "tkelley via AccessMonster.com" <u47368[ at ]uwe>
>wrote:
>> Is this all a local database, run on each user's local machine?
>>
>[quoted text clipped - 29 lines]
>> --
>> Message posted via AccessMonster.comhttp://www.accessmonster.com/Uwe/Forums.aspx/access-forms/200812/1
>
>Yes, it is a local access database on a shared network drive. Yes,
>the users have rights to the folder. It is weird because the one user
>who is having problems is the senior manager and the other is the
>senior trade specialist. This [seems to be] the only problem these
>two users are having with the application.

--
Message posted via AccessMonster.com
http://www.accessmonster.com/Uwe/Forums.aspx/access-forms/200812/1

Re: Why Would A Dlookup Function Work On One Computer But Not On Another Computer?

"Douglas J. Steele" <NOSPAM_djsteele[ at ]NOSPAM_gmail.com> 12/31/2008 9:07:20 PM

If it isn't a FE/BE, it should be. Users should never share the same
application database.

Once each user has his/her own copy of the front-end, ideally on his/her
hard drive, check to ensure that the References collection is okay for each
of the users having a problem.

--
Doug Steele, Microsoft Access MVP
http://I.Am/DougSteele
(no private e-mails, please)

"tkelley via AccessMonster.com" <u47368[ at ]uwe> wrote in message
news:8f805446bee2d[ at ]uwe...
[Quoted Text]
> Is it FE/BE with table links? If so, you're sure the users in question
> have
> the most current link? (If you had added a field referenced in the
> criteria
> of the DLookup, and they don't have current links ...)
>
> Are they power-users? Have they been dinking around in the design where
> they
> shouldn't have been? You've tried a fresh, new copy of the database on
> their
> machine that is an EXACT copy of the one that works on yours?
>
> Just throwing more stuff out there ...
>
> R Tanner wrote:
>>On Dec 31, 1:32 pm, "tkelley via AccessMonster.com" <u47368[ at ]uwe>
>>wrote:
>>> Is this all a local database, run on each user's local machine?
>>>
>>[quoted text clipped - 29 lines]
>>> --
>>> Message posted via
>>> AccessMonster.comhttp://www.accessmonster.com/Uwe/Forums.aspx/access-forms/200812/1
>>
>>Yes, it is a local access database on a shared network drive. Yes,
>>the users have rights to the folder. It is weird because the one user
>>who is having problems is the senior manager and the other is the
>>senior trade specialist. This [seems to be] the only problem these
>>two users are having with the application.
>
> --
> Message posted via AccessMonster.com
> http://www.accessmonster.com/Uwe/Forums.aspx/access-forms/200812/1
>

Re: Why Would A Dlookup Function Work On One Computer But Not On Another Computer?

R Tanner <tanner.robin[ at ]gmail.com> 12/31/2008 9:49:16 PM

On Dec 31, 2:07 pm, "Douglas J. Steele"
<NOSPAM_djsteele[ at ]NOSPAM_gmail.com> wrote:
[Quoted Text]
> If it isn't a FE/BE, it should be. Users should never share the same
> application database.
>
> Once each user has his/her own copy of the front-end, ideally on his/her
> hard drive, check to ensure that the References collection is okay for each
> of the users having a problem.
>
> --
> Doug Steele, Microsoft Access MVPhttp://I.Am/DougSteele
> (no private e-mails, please)
>
> "tkelley via AccessMonster.com" <u47368[ at ]uwe> wrote in messagenews:8f805446bee2d[ at ]uwe...
>
> > Is it FE/BE with table links? If so, you're sure the users in question
> > have
> > the most current link? (If you had added a field referenced in the
> > criteria
> > of the DLookup, and they don't have current links ...)
>
> > Are they power-users? Have they been dinking around in the design where
> > they
> > shouldn't have been? You've tried a fresh, new copy of the database on
> > their
> > machine that is an EXACT copy of the one that works on yours?
>
> > Just throwing more stuff out there ...
>
> > R Tanner wrote:
> >>On Dec 31, 1:32 pm, "tkelley via AccessMonster.com" <u47368[ at ]uwe>
> >>wrote:
> >>> Is this all a local database, run on each user's local machine?
>
> >>[quoted text clipped - 29 lines]
> >>> --
> >>> Message posted via
> >>> AccessMonster.comhttp://www.accessmonster.com/Uwe/Forums.aspx/access-forms/200812/1
>
> >>Yes, it is a local access database on a shared network drive. Yes,
> >>the users have rights to the folder. It is weird because the one user
> >>who is having problems is the senior manager and the other is the
> >>senior trade specialist. This [seems to be] the only problem these
> >>two users are having with the application.
>
> > --
> > Message posted via AccessMonster.com
> >http://www.accessmonster.com/Uwe/Forums.aspx/access-forms/200812/1

I am using a split database, and these guys are not power users. They
don't know the first thing about access. I have made sure they have
the exact same copy of the front end I have. I have not verified they
have the correct references enabled in their access client. I will
check that. It seems weird that would be the problem though because I
am using a win32 api call that doesn't have any problems on their
machines. Not to mention the fact that I have references to the
outlook client object library model. I will check and post back on
Friday though.

If you have any other ideas, please let me know. The other users that
are using this application have much less rights and they don't have
any problems.

Re: Why Would A Dlookup Function Work On One Computer But Not On Another Computer?

"tkelley via AccessMonster.com" <u47368[ at ]uwe> 12/31/2008 10:20:33 PM

Well good luck. If it's not a reference issue, my last ditch idea would be
to:

Create a new form, copy your objects & code over so that you have a duplicate
copy with duplicate functionality (but not by using 'Save As' -- by creating
it new from scratch, then copying the stuff in).

Compile, compact, etc., then have them try the new form.

I have encountered instances where there is just a ghost in the machine, and
this can often clear it up ... for no logical, known reason. I've recently
had a report that would not print in color from one users machine. No matter
what printer it was sent to, it would only print in black and white. But
when I printed it from my machine to the same printers ... color.

So I created a new report, did like I suggested to you, then--presto--it
worked. I can't tell you why, but the problem went away and hasn't come back.
It's rare, but I've had similar hiccups in forms fixed the same way.

In any event, once you find out what fixes it, report back. Cuz I'm not
going to be able to sleep until you do : )

R Tanner wrote:
[Quoted Text]
>On Dec 31, 2:07 pm, "Douglas J. Steele"
><NOSPAM_djsteele[ at ]NOSPAM_gmail.com> wrote:
>> If it isn't a FE/BE, it should be. Users should never share the same
>> application database.
>[quoted text clipped - 39 lines]
>> > Message posted via AccessMonster.com
>> >http://www.accessmonster.com/Uwe/Forums.aspx/access-forms/200812/1
>
>I am using a split database, and these guys are not power users. They
>don't know the first thing about access. I have made sure they have
>the exact same copy of the front end I have. I have not verified they
>have the correct references enabled in their access client. I will
>check that. It seems weird that would be the problem though because I
>am using a win32 api call that doesn't have any problems on their
>machines. Not to mention the fact that I have references to the
>outlook client object library model. I will check and post back on
>Friday though.
>
>If you have any other ideas, please let me know. The other users that
>are using this application have much less rights and they don't have
>any problems.

--
Message posted via AccessMonster.com
http://www.accessmonster.com/Uwe/Forums.aspx/access-forms/200812/1

Home | Search | Terms | Imprint Contact

Newsgroups Reader - provided by WiredBox.Net