A VERY weird form value parsing bug

[dspitzle]

I've got a very weird and confusing bug here. Stripping it down to the core problem I've isolated, I have a database accessible by several users, including myself. There is a form containing several records, and one of the fields on the form is the record ID. I build a query which reports the value of the ID field for the current record (i.e. a column of form

Exp1: Forms![Form_Name]![Field_Name]

with a PARAMETER line defining Forms![Form_Name]![Field_Name] as a Long Integer
).

If I open the database and run the query, the query returns the ID of the current record on the form.

If my users open the database and run the query, the query returns a 0.

WTF! I've confirmed this with my own eyes and still can't believe it.

I'll note we're logging into the same machine (it's a virtual server arrangement via Citrix), so all of the Windows and Office infrastructure is identical, and there is no Access security in place. The only thing I can figure is that there are some sort of user-specific Windows security settings that are being loaded that prevent the form field references from being parsed, but I have no idea how to pin down the problem. Any suggestions of other things to try?

 

[kjv1611]

Seems like I saw someone else having issues with Access on Citrix, and that there was at least one link posted referencing a known issue there... not sure if it's related.

Try searching on Access on Citrix possibly..

--

"If to err is human, then I must be some kind of human!" -Me

 

[dspitzle]

I'm not having any luck finding a similar problem in the posts here. More to the point, it can't specifically be Citrix that's at fault, as I can get the correct results over Citrix. It's the fact that different users are getting different results that's the problem; the fact that Citrix is involved doesn't seem particularly germaine to the problem.

 

[maxhugen]

I've recently been looking into virtual private servers myself, and whilst I know little about them or Citrix really, a colleague came across an interesting situation using virtual machines in Windows 7 (beta).

Essentially, we determined that she was not seeing the most recent data, and we suspect that it's due to a caching issue (or something like that) by the virtual machine.

I don't know if this is related to your issue, but I'd definitely explore that possibility with Citrix.

HTH

Max Hugen
Australia

 

[dspitzle]

I suspect that's unlikely, as the data file itself is stored on a different server than the one that's been virtualized, so Citrix would have to be storing an out of date copy of one particular network-accessed file, only displaying it to certain users.

 

[maxhugen]

OK, more guesswork...

Is the form returning the same number of records for your user as for you?

Is your db split into a FE and a BE? If so, where is the FE stored? Same location as the BE?

Max Hugen
Australia

 

[dspitzle]

OK, more guesswork...

Is the form returning the same number of records for your user as for you?

Is your db split into a FE and a BE? If so, where is the FE stored? Same location as the BE?
----------------------

Yes, we see the same number of records on the form, and no, for this particular application the front end and back end are unified in one .mdb file.

 

[kjv1611]

for this particular application the front end and back end are unified in one .mdb file.

Um, so it's not split.

--

"If to err is human, then I must be some kind of human!" -Me

 

[TheAceMan1]

How are ya dspitzle . . .

Although I've never used Citrix ... nor have I ever had to use virtual private servers ... Logic tells me there's Citrix functionality, Access fuctionality, and what ever functionality exists between the two. I'm believing that once the form is open the [blue]record ID[/blue] should be available thru record ID[blue]access functionality[/blue] ... Such as:

[blue]   Me!TextboxName = Me![Record ID][/blue]

[blue]your thoughts? . . .[/blue]


See Ya! . . . . . .

Be sure to see thread181-473997 [blue]Worthy Reading![/blue]
Also faq181-2886 [blue]Worthy Reading![/blue]

 

[dspitzle]

That's where it is failing. The query is able to resolve the form field reference when I run it, but for my users the query fails to resolve it, and returns a 0 for evaluation in the query. Visual Basic, however, is able to return the value in the field, so my guess is that something isn't getting passed to the Jet database engine.