Forms Mortally Slow

[a a r o n . k e m p f]

Excuse me-- wall of negativity?

Maybe if Jet was reliable enough for businesses to trust-- then maybe
there wouldnt' be a wall of negativity.
Maybe if I didn't get crucified for encouraging people to upsize to a
reliable, secure platform-- maybe if I didn't get crucified for
reccomending SQL Server-- then maybe there wouldn't be a wall of
negativity.

But as it is, these so called professionals are trying to get you
stuck on the same sinking boat-- it's like-- instead of jumping off of
the sinking titanic- you're pleading for more people to come onto the
titanic..
WHEN ALL IT IS IS A SINKING WORTHLESS SHIP.

Jet fucking sucks balls.

-Aaron

 

[a a r o n . k e m p f]

Gina;

that is perfectly relevent. Jet hasn't had any updates in a decade.

So sorry that MIcrosoft hasn't fixed decades-old Jet corruption /
stability problems

 

[BruceM]

Wrong again, as you are perfectly well aware.

message
Gina;

that is perfectly relevent. Jet hasn't had any updates in a decade.

So sorry that MIcrosoft hasn't fixed decades-old Jet corruption /
stability problems

 

[Gina Whipp]

Aaron,

Nope, just your normal trash...

--
Gina Whipp

"I feel I have been denied critical, need to know, information!" - Tremors
II
message
Gina;

that is perfectly relevent. Jet hasn't had any updates in a decade.

So sorry that MIcrosoft hasn't fixed decades-old Jet corruption /
stability problems

 

[John... Visio MVP]

in message
want a stupid workaround.

Move to SQL Server

moving to SQL Serve is a stupid workaround?

John...

 

[a a r o n . k e m p f]

JET STILL CORRUPTS
JET STILL REQUIRES _THREE_ TIERS OF LINKED DATABASES TO DO _ANYTHING_
JET REQUIRES MOUNTAINS OF VBA CODE TO HANDLE STUFF THAT IS BUILT IN TO
SQL SERVER

SQL Server allows your databases to automagically link each other.

It's drop dead simple, it's fast, it's easier than Jet.

It's faster than Jet.
And it's 'MORE FREE' then Jet.

So sorry that your'e too stupid to learn the worlds most popular
database

 

[Gina Whipp]

You're like a child when things don't go your way aren't you? Rhetorical
question, no need to reply!

--
Gina Whipp

"I feel I have been denied critical, need to know, information!" - Tremors
II
message
JET STILL CORRUPTS
JET STILL REQUIRES _THREE_ TIERS OF LINKED DATABASES TO DO _ANYTHING_
JET REQUIRES MOUNTAINS OF VBA CODE TO HANDLE STUFF THAT IS BUILT IN TO
SQL SERVER

SQL Server allows your databases to automagically link each other.

It's drop dead simple, it's fast, it's easier than Jet.

It's faster than Jet.
And it's 'MORE FREE' then Jet.

So sorry that your'e too stupid to learn the worlds most popular
database

 

[Ray S.]

Bigger problem now...I followed the Allen Browne instructions on library
references and updated them...now my import data wizard doesn't work. It
gives an error saying "there is no object in this control." I read the
Knowledge Base info on fixing that and it did not work...now I'm really
screwed...any help to get back is greatly appreciated. I ran the installer
and repaired the installation successfully, but that did not fix it. HELP!

 

[BruceM]

What references do you have now? What happens if you revert to the
references you had previously?

You say you ran the installer? Is that the Access installation program, or
what exactly? Did you try Allen's recovery sequence?

I am not familiar with the import data wizard, and did not attempt to answer
anything about that. For that matter, I don't see where you mentioned it in
the thread until now. I can say that turning off Name AutoCorrect will not
have an effect on problems already caused by that "feature". That is why
Allen lists a full recovery sequence, starting as I recall with a backup of
the existing database file.

 

[Ray S.]

When I check the library references, none are "missing." The current problem
of not being able to either link or import external data is now more serious
to me than the prior problem. Are the library references specific to the
database? If so, I had a backup of the database, but opening it I have the
same problem - when you go to the file menu and select get external file, I
can't perform either of the options (import or link). In either case, I get
an error dialog saying "object has no control" and then the wizard dialog
comes up almost all whited out. Since this was the case in both the current
and the backup copies of the database, I think that something I did when I
was following the library references update instructions is what caused this
whole thing to bomb. When I say installer, I mean that I went to the
Microsoft Office Installer and tried to repair the installation. That didn't
work either. Now I'm figuring that I'll uninstall Office completely and try
re-installing it. I'm at a real loss here because everything I read suggested
there was an easy fix to this problem - but none of the offered solutions
have worked. Any ideas? I can do away with the forms completely, but I can't
get away from having to import comma delimited and excel files into the
database.

 

[James A. Fortune]

When I check the library references, none are "missing." The current problem
of not being able to either link or import external data is now more serious
to me than the prior problem. Are the library references specific to the
database? If so, I had a backup of the database, but opening it I have the
same problem - when you go to the file menu and select get external file, I
can't perform either of the options (import or link). In either case, I get
an error dialog saying "object has no control" and then the wizard dialog
comes up almost all whited out. Since this was the case in both the current
and the backup copies of the database, I think that something I did when I
was following the library references update instructions is what caused this
whole thing to bomb. When I say installer, I mean that I went to the
Microsoft Office Installer and tried to repair the installation. That didn't
work either. Now I'm figuring that I'll uninstall Office completely and try
re-installing it. I'm at a real loss here because everything I read suggested
there was an easy fix to this problem - but none of the offered solutions
have worked. Any ideas? I can do away with the forms completely, but I can't
get away from having to import comma delimited and excel files into the
database.

See:

http://groups.google.com/group/comp.databases.ms-access/msg/354d6d6c612aca3e

If you have a backup of your registry, try that first. If not, try
going back to the last restore point before you tried to fix the Access
references. There are certain registry settings that an Access install
won't change, even if they're wrong. In fact, I think I'll back up my
registry and also create a restore point right now just to be safe.

James A. Fortune
(e-mail address removed)

 

[BruceM]

Is the problem with just this database, or with all databases? If the
former, reinstalling Office most likely will not help. Instead, see the
steps to recover the database in the link I provided. Please read them
carefully, and follow them exactly as written.

My question about references is what specific references you have.

I did a search about the error message and found the following from a
posting. There were several other postings that suggested the same thing:

***********
"If the import/export wizards don't work at all, or if you get "No object
in this control" re-register ACCWIZ.DLL.

If it's one or more file formats that aren't listed, re-register the
following files
msexcl40.dll (Excel)
msxbse40.dll (dBase)
mspdox40.dll (Paradox)
mstext40.dll (Text, CSV, tab-delimited))
In Access 97, the filenames contain 35 instead of 40.


To re-register a DLL file,


1) Locate it (usually all these are in the Windows\System32 or
WINNT\System32 folder.


2) Locate the file regsvr32.exe.


3) Drag the DLL file's icon onto the regsvr32.exe icon."

***********

 

[a a r o n . k e m p f]

wow-- sounds to me like you've got _QUITE_ the mess of Jet databases.
and you've got downtime.

Just remember-- Real Companies-- and Real Developers-- use a real
database-- because Jet fucking sucks.

-Aaron

 

[a a r o n . k e m p f]

library databases are pointless.

keep your stored procedures and your tables where they belong-- on a
database server-- and all your config problems magically go away

 

[BruceM]

Since you rarely if ever have any practical suggestions you should keep
quiet. Even a "magic" database needs to be developed. Your "suggestion" in
this case, as with most others, is irrelevant to the question at hand.

message
library databases are pointless.

keep your stored procedures and your tables where they belong-- on a
database server-- and all your config problems magically go away

 

[a a r o n . k e m p f]

You're the one that insists that everyone stick to an impractical
database format 'just because BruceM is too fucking stupid to learn
the worlds most popular database'

Maybe you should learn some more about the worlds most popular
database (SQL Server) before you worry about trying to tell me who is
practical and who isn't.

THanks

-Aaron