Until recently, I had Access 2002 available for testing, but something has
resulted in it being "in need of repair" (possibly installing Access 2010),
so I am not in a position to see if I can re-create the problem.
--
Larry Linson, Microsoft Office Access MVP
Co-author: "Microsoft Access Small Business Solutions", published by Wiley
Access newsgroup support is alive and well in USENET
comp.databases.ms-access
"croy" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> On Mon, 11 Jul 2011 13:37:57 -0500, "Access Developer"
> <(E-Mail Removed)> wrote:
>
>>Historically, the advice usually given with any "display anomaly" is to
>>obtain the latest drivers from the manufacturer/provider of your graphics
>>/
>>display hardware. Sometimes it actually works; in other instances it's
>>just
>>"one of the things we try and eliminate as a possible contributor to the
>>problem; in rarer cases, it causes even worse problems. On the assumption
>>that Murphy was correct, I wouldn't recommend it, but simply note that it
>>is
>>often suggested.
>
> Thanks for the reply.
>
> While I wouldn't rule out the possibility of hardware
> drivers being the problem, I'm thinking that it's more
> likely an Access problem, because.... When I first open the
> form, the lines display correctly. It's only after moving
> to a different record that they all disappear, until each
> field is visited, when the line for that field will
> reappear.
>
> This is on a work computer, so according to the rule-book, I
> should call the IT department. But experience has shown
> that they will simply throw a stock image back on, costing
> me days to get things just partially back to my way of
> working.
>
> Maybe I'll boot to my imaging disk and make an image of the
> drive, then boot back to WindowsXP and install the latest
> graphics drivers, and see if there's a difference.\
>
> The drivers are possibly and issue. This is Gateway/nVidia
> box, and Gateway says nothing new. nVidia has something
> newer, but I can't determine if it's anything this box would
> benefit from or not.
>
> A lot of work for, what I think, is a slight chance of
> improvement. Probably less work to assume that this version
> of Access doesn't do lines correctly, and figure some other
> way to get the effect I want.
>
> --
> croy
|