I've had trouble on some machines getting Access 2007 to associate
itself with older mdb files and in these cases have had to resort to
opening the older files from within Access instead of from Explorer.
Yes, it makes no sense. Anyway, it seems from your description you
don't have this probl
Have you tried running the application on a PC without ANY version of
Office installed? If the application runs w/o Office installed try
running the application after installing all MS Office applications
EXCEPT MS Access. If that works then you can either:
1. Leave the system set up withou
Well, if you can't find an export function, maybe just print the darn
thing out and scan it back in? I dunno what else to suggest.
On Thu, Oct 2, 2008 at 12:52 PM, Larry Sacks <[EMAIL PROTECTED]> wrote:
> I can open it on his old system *BUT* not by going directly into MS
> Access 2000. If I try
Assuming this is what you meant:
I changed the shortcut on my system to point to the latest version of MS Access
(not the runtime) and included the rest of the goodies from the shortcut
(basically invoke MS Access 2007 instead of the MS Access Runtime). When I do
that, it actually loads the d/
Hello all:
I believe that opening a runtime application will be successful if the
underlying code of the runtime application is compatible with the version of
access trying to open it. But the best chance I believe is to open the latest
version of access possible and then to point to the mdb fi
I can open it on his old system *BUT* not by going directly into MS
Access 2000. If I try to open it, I get the permissions error again.
Instead I can open it via the shortcut.
When this d/b delivered, it used the MS Access Runtime 2000 so you
didn't have to have Access installed.
Oh... and the
Didn't you just say you can open it on his old machine? Then can't you
just export it as a csv?
On Thu, Oct 2, 2008 at 11:38 AM, Larry Sacks <[EMAIL PROTECTED]> wrote:
> I've been through the MS newsgroups, but I'll wade through them again.
> The solutions that sound plausible involve getting the
I've been through the MS newsgroups, but I'll wade through them again.
The solutions that sound plausible involve getting the original version
of access, although how do I go about finding that? The software was
installed in 2001.
Sending you the file is an interesting idea, but the file has
The usual time I see this error is when you load a piece of software
that emulates a CD.
Something got loaded that is preventing the system fro
reading/addressing the CD machine.
Stewart
At 09:20 AM 10/2/2008, you wrote:
>The driver may be corrupted or missing. (Code 39)" This time, the
>
>The driver may be corrupted or missing. (Code 39)" This time, the
>Windows help message has changed. It says to uninstall the device
>driver and then do a new hardware search.
That is the usual way to solve this. Sometimes you need to remove
multiple drivers because they interact. Sometimes
>She could boot from a DVD to upgrade the OS and install software. That
>was when the DVDs mounted.
Great. You have established that:
1) The drive works
2) The drive is able to read DVD format
Next thing to try is booting into safe mode (startup with shift key
down). That should prevent any sec
>Is there software that would make it not recognize DVDs while CDs mount OK?
Unlikely, but I never say never when it comes to software or driver
induced problems. Can you boot from a DVD containing the OS? That would
rule this out.
The problem could be accumulated dust or a hairball inside t
> Well, I'd do my part, but the *&%^ing Verizon site won't allow me to add
> the DVR option when ordering FIoS. It always errors out saying that the
> number of set top boxes doesn't match the number of TVs to be connected
> (it does). I've tried it both IE and Firefox. And of course, the sales
13 matches
Mail list logo