Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Access XP Worst Yet

Status
Not open for further replies.

aaahhhrrggghhhh

Programmer
Apr 5, 2002
61
IE
Hi.

I have Access XP (SR-2), and it stinks. I have created a report. This report has a recordsource. The recordsource has a reference to a control on a open form. Whatever the value of the control, the recordsource still recieves Null.

Heres the SQL:

SELECT *
FROM NEWLTT_FULLPROP, ORGANISATION
WHERE (((Len([NEWLTT_FULLPROP].[Full Proposal Ref No]))>19) AND ((NEWLTT_FULLPROP.[Promoting Org])=[ORGANISATION].[INTERNAL_ID]) AND ((NEWLTT_FULLPROP.Eligible)=Yes) AND ((NEWLTT_FULLPROP.RoundID)=Trim([Forms]![Reports Menu]![cbRoundSel])));

See where it says ((NEWLTT_FULLPROP.RoundID)=Trim([Forms]![Reports Menu]![cbRoundSel]))), well, this always equates to Null, even if the control cbRoundSel is selected. I have entered Debug.Print [Forms]![Reports Menu]![cbRoundSel] from the Immediate window, and its fine.

So, now you all know how rubbish Access XP is now, I can tell you how I resolved it. Making global variables, and populating them when the value of the control changes. Thanks Microsoft for making it so damned difficult!

An Upset Chappy. Dont be small. be BIG
 
You might want to try

[Forms]![Reports Menu].cbRoundSel

Not sure if it'll help much though. --------------------------------------
It's not the monsters under your bed, it is the men next door.
That make you fear, make you cry. Make you cry for the Child.
All the wars are fought amongst those lonely men. Unharmed, unscarred.
 
Thanks for the help, but the . operator is used to expose properties rather than embedded controls, so that doesn't work. Another thing that I don't understand about Microsoft is .. when it works, they change it .. why??

Eg. The search mechanism in Access 97 is really good and provides mostly the information (if not too much) that you want. The new XP search mechanism for all the office XP products is a waste of time as you NEVER get the information you want, and the cursor keeps stopping. The usability of the search mechanism is so bad that I have had to uninstall it permanently, and rely on information on the web. This is OK if your in a business on a leased line, but if your a home user it can be extreemly expensive. I'm not just talking about Access XP, but the whole of OfficeXP in total.

Also, in Word XP, if you want to run a mail merge from a public outlook folder, dont. You can't. You have to open outlook and go through the tools menu to do so! Ha! What fools. Do they not know there ARE people out there who don't want to spend all their time on the web researching simple tasks in a suite that is supposed to be very usable by even idiots with 1 bacteria for a brain. Developers find it awkward enough without microsoft swapping everything around. Is it that they get some extra money for causing such confusion ... ahh, yes, you have to pay to use their customer service even though you bought their rubbish product, typical materialistic demons from hell.

See if I care!

What rubbish XP is.


Dont be small. be BIG
 
Hmmm... Then how about [Forms]![Reports Menu]![cbRoundSel].value?

About your opinions on Microsoft... Not gonna go into it again... Everything has it's good and it's bad sides.

--------------------------------------
It's not the monsters under your bed, it is the men next door.
That make you fear, make you cry. Make you cry for the Child.
All the wars are fought amongst those lonely men. Unharmed, unscarred.
 
Access XP is pretty darn good in my experience. I don't know what is causing the problem the original poster described, but it is most assuredly NOT Access XP.

Original Poster--Have you checked all of the column related properties of your combo box? What happens if you leave the form open, go to the immediate window, and type
?[Forms]![Reports Menu]![cbRoundSel]

Next, what happens when you wrap that in the trim function?

Jeremy =============
Jeremy Wallace
Designing, Developing, and Deploying Access Databases Since 1995

Take a look at the Developer's section of the site for some helpful fundamentals.
 
OK, OK, so I was a little rash, but I still hold my ground on the search mechanism. The problem was resolved. It was rubbish data that caused the problem. However, I must point out a few other important things :

* If you create a listbox in a form (details section), and populate it with data, it occasionally has a tendancy to resize itself. You will have to put the .height and .width property settings every time you populate it, just to make sure ... oh, and the scale type (centimeters or pts) defaults to points, so you need to find out what 1 inch is in centimeters, then multiply that by its size before you get the correct settings. Had a hillarious time with that.

* Also, the refresh rate of the form causes bits to disappear, or you may find your active desktop becoming the new seasons fashion as far as your GUI is concerned.

* Heres a good one. My collegue opened her database and all her tables were gone, so were her queries etc. Well, they weren't ACTUALLY gone, its just that the refresh rate of Access (i think) caused them to disappear. They were there really. (Bit of a houdini act this one!)

Will post any more findings.

So, count my original post as being sorted, thanks to all your contributions. I have heard though, through collegues that the mail merging is dodgy in Word XP, so I'm looking forward to the whole new XP XPerience!

Dont be small. be BIG
 
I agree with you about XP, I have had loads of problems with it including the fact that one of my forms does not work if you run it maximised but if you make the window smaller it does !!! How strange is that ?

Justin
 
Justin,

Start a thread about your form, giving a full description of the problem (what is supposed to happen, what actually happens). I'll bet you a beer we find the solution, and that it's not a bug in XP (even if the same form works just fine in other versions).

Jeremy =============
Jeremy Wallace
Designing, Developing, and Deploying Access Databases Since 1995

Take a look at the Developer's section of the site for some helpful fundamentals.
 
Hi Jeremy

I tried that but no-one replied. As I have a deadline and compatability issues with other users I have decided to drop the Access forms and try using ASP. I guess this is what I should have done in the first place.

Thanks for your help though Jeremy

Regards
Justin
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top