Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion GroupsFormsForms ProgrammingQueriesModules / DAO / VBAReports / PrintingMacrosDatabase DesignSecurityConversionImporting / LinkingSQL Server / ADPMultiuser / NetworkingReplicationSetup / ConfigurationDeveloper ToolkitsActiveX ControlsNew UsersGeneral 1General 2
Access DirectoryToolsTutorialsUser Groups
Related Topics
SQL ServerOther DB ProductsMS OfficeMore Topics ...

MS Access Forum / General 1 / January 2006

Tip: Looking for answers? Try searching our database.

Problems while making MDE

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
CTI - 03 Jan 2006 07:29 GMT
I got problems when I want to make a MDE file. The app. got a lack of
memory.

Bart
Access 2003
Steve - 03 Jan 2006 15:22 GMT
Bart,

Amazingly enough, the solution to this problem is to 1) shut down every
possible program on your system when you wish to create your MDE, or 2)
buy more memory. Please note that you must also install said memory -
simply purchasing it will not do the trick.

If neither of these solutions takes care of your problem, you may need
to discharge the static electricity buildup in your CPU. The steps for
doing this are as follows:
1. Make sure your computer is turned on and your monitor is turned off.
2. Hold your computer about 10 inches above the desk surface. Keep a
firm grip.
3. Drop the system onto the desktop. Make sure it lands flat and not to
one side.
4. Repeat Step 3 15-20 times, then check to see if your static
electricity buildup is gone. If not, repeat Step 3 10 more times.
5. Read BOFH.
Larry Linson - 03 Jan 2006 15:48 GMT
>I got problems when I want to make a MDE file. The app. got a lack of
>memory.

I suggest you do not follow Steve's instructions.

Generally, problems in making MDEs are the result of compilation errors in
your MDB. Go into the MDB's module windows, and Compile. Fix the errors, and
see if that takes care of your difficulty.

 Larry Linson
 Microsoft Access MVP
Steve - 03 Jan 2006 17:41 GMT
Yes, I suggest that you don't actually follow my suggestion as well,
except the part about getting more memory or closing open programs. If
you're getting an error about insufficient memory, chances are good
that your system does not have enough memory to make the MDE. You may
want to try making the MDE on another, better machine before spending
money on new RAM, though.

You may want to read BOFH anyway, for kicks.
David W. Fenton - 03 Jan 2006 20:36 GMT
> Yes, I suggest that you don't actually follow my suggestion as
> well, except the part about getting more memory or closing open
> programs. If you're getting an error about insufficient memory,
> chances are good that your system does not have enough memory to
> make the MDE. . . .

Malarkey.

> . . . You may
> want to try making the MDE on another, better machine before
> spending money on new RAM, though.

Most "out of memory" errors on Windows are not about insufficient
RAM, which because of virtual memory and swap files is incredibly
hard to use up, but because of resource problems. It can also be
caused by corrupt files causing a process to go into a loop that
uses up memory.

This latter is the more likely scenario, and is the reason Larry
suggests compiling the MDB before attempting to create the MDE.

Your suggestions betray a lack of understanding of both Windows
hardware/software and Access MDEs.

Signature

David W. Fenton                  http://www.dfenton.com/
usenet at dfenton dot com    http://www.dfenton.com/DFA/

Keith Wilby - 04 Jan 2006 09:31 GMT
> Your suggestions betray a lack of understanding of both Windows
> hardware/software and Access MDEs.

Betray?  Display perhaps.
Steve - 04 Jan 2006 14:16 GMT
First of all, I've made it no secret that I do not understand or work
with Access MDEs.

Second, nearly every 'out of memory' or 'insufficient memory' error I
have ever gotten was actually a result of the system running out of
resources. Perhaps your version of Windows was programmed by more
malicious Microsoft coders than mine who one day decided to switch all
the error messages around so you'd never really know what the true
problem is or how to fix it.

To quote you:
"It can also be
caused by corrupt files causing a process to go into a loop that
uses up memory. "

Uses up memory? Yes, that sounds like something that would cause an
'out of memory' error...because it's using up all the memory available.

Your response indicates a lack of proofreading.
Keith Wilby - 04 Jan 2006 14:59 GMT
> Your response indicates a lack of proofreading.

BTW Steve I was in no way agreeing with David in my response, merely
pointing out an example of poor diction.  No-one is perfect, some people
need to tell themselves that more often.
Steve - 04 Jan 2006 16:19 GMT
Understood, Keith. My own obsession with language and its use causes me
to do the same thing.

With a bit of irony I was about to point out that 'diction' is usually
practiced in a verbal sense, but that it technically applies to both
the written word and the spoken one. Touché.
Keith Wilby - 04 Jan 2006 16:45 GMT
> Understood, Keith. My own obsession with language and its use causes me
> to do the same thing.

It occurs to me now that the word he may have been searching for is
"portray" but I guess we'll never know as I'm in his killfile ;-)
Steve - 04 Jan 2006 17:26 GMT
While David seems to have quite a bit of knowledge to share on the
topic of MS Access, the allegations that have been brought out
concerning a pedophilic appetite for underage males cause me to be very
careful of accepting information from him at face value. I realize that
that Access and the personal life are two very distinct areas for most
people, but to me the allegations about David's personal life seem to
overshadow his contributions that aren't strictly about Access.

David, you are welcome to put me in your killfile; I will still be able
to read your posts, which works for me as the knowledge seems to flow
much harder from your side than mine.

Note that I do not intend to hijack this post, nor am I making any
accusations.
Tim Marshall - 04 Jan 2006 17:43 GMT
> While David seems to have quite a bit of knowledge to share on the
> topic of MS Access, the allegations that have been brought out

You are a f.cking a.shole.  SO he's not diplomatic when he trashes you,
there's no need to be a total a.s pick from some dark hole.

<PLONK>
Signature

Tim   http://www.ucs.mun.ca/~tmarshal/
^o<
/#) "Burp-beep, burp-beep, burp-beep?" - Quaker Jake
/^^ "What's UP, Dittoooooo?" - Ditto

Tim Marshall - 04 Jan 2006 18:10 GMT
> You are a

Apologies to all for the profanity.
Signature

Tim   http://www.ucs.mun.ca/~tmarshal/
^o<
/#) "Burp-beep, burp-beep, burp-beep?" - Quaker Jake
/^^ "What's UP, Dittoooooo?" - Ditto

David W. Fenton - 04 Jan 2006 19:53 GMT
>> You are a
>
> Apologies to all for the profanity.

Sometimes profanity is the only way to express what needs to be
said.

If profanity had no utility, it never would have been invented.

Signature

David W. Fenton                  http://www.dfenton.com/
usenet at dfenton dot com    http://www.dfenton.com/DFA/

Tim Marshall - 04 Jan 2006 22:12 GMT
> Sometimes profanity is the only way to express what needs to be
> said.
>
> If profanity had no utility, it never would have been invented.

I'm a former army officer - believe you me, profanity is a wonderful
thing that saves me from having to think about adverbs and adjectives,
but I've found in my 14 years of civilian life it tends to upset
people... 8)  When I do get involved in a project with another former
tanker it's wonderful to be able to swear like a soldier again without
having to worry about causing offense...

Signature

Tim   http://www.ucs.mun.ca/~tmarshal/
^o<
/#) "Burp-beep, burp-beep, burp-beep?" - Quaker Jake
/^^ "What's UP, Dittoooooo?" - Ditto

Steve - 04 Jan 2006 18:57 GMT
I think Tim missed the point there...I don't believe I said anything
about David trashing me...

Either way, I can now relax with killfiled joy.
David W. Fenton - 04 Jan 2006 19:52 GMT
>> While David seems to have quite a bit of knowledge to share on
>> the topic of MS Access, the allegations that have been brought
[quoted text clipped - 4 lines]
>
><PLONK>

I beat you to the PLONK.

I had been wondering for several days who this STEVE was, I had
first thought it was perhaps PC Datasheet attempting to launch a new
identity, free of the old associations, but the responses were too
stupid. I then started thinking it was possibly another Don Mellon
sock puppet.

The pedophile reference pretty much proves it, as the only person
who has shown an interest in that subject in these precincts is Don
Mellon.

Signature

David W. Fenton                  http://www.dfenton.com/
usenet at dfenton dot com    http://www.dfenton.com/DFA/

Steve - 04 Jan 2006 20:36 GMT
Eh, I came back to apologize and here I'm already killfield. OK by me.

My name is actually Steve. The only reason I made the pedophile
reference is because of content posted to another newsgroup that was
supposedly taken from David Fenton's own post. I tend to disbelieve
most things of that nature, but the content posted was so disgusting
that I have to at least consider the possibility that it is true, if
carefully.

David, though I haven't attacked you, I do apologize for even writing
the post. I let my own foul mood get the best of me and it came out in
the form of poor judgement. Whether or not you killfile me is your
business. As I said before, most of the knowledge posted by you
supercedes my own, so that information flow will not change.
rkc - 04 Jan 2006 21:39 GMT
> While David seems to have quite a bit of knowledge to share on the
> topic of MS Access, the allegations that have been brought out

Totally uncalled for Steve. You should be ashamed.
Steve - 04 Jan 2006 22:32 GMT
I notice that no one has actually addressed the issue I (shouldn't
have) raised. Perhaps blind faith isn't all it's cracked up to be.
rkc - 04 Jan 2006 23:08 GMT
> I notice that no one has actually addressed the issue I (shouldn't
> have) raised. Perhaps blind faith isn't all it's cracked up to be.

It's irrelevant.
David W. Fenton - 05 Jan 2006 01:50 GMT
>> I notice that no one has actually addressed the issue I
>> (shouldn't have) raised. Perhaps blind faith isn't all it's
>> cracked up to be.
>
> It's irrelevant.

It's also an accusation based on a complete falsehood that has been
refuted many times, and not just by me.

This is clearly a Don Mellon sock puppet again. Killfile him and
ignore him and all will be well for everyone.

Signature

David W. Fenton                  http://www.dfenton.com/
usenet at dfenton dot com    http://www.dfenton.com/DFA/

Keith Wilby - 05 Jan 2006 08:46 GMT
> While David seems to have quite a bit of knowledge to share on the
> topic of MS Access, the allegations that have been brought out
> concerning

Umm, David and I may not see eye to eye on certain issues but I don't think
it was necessary to rake up all of that.
Steve - 05 Jan 2006 13:53 GMT
I accused no one.

I have yet to see anything David has written to contradict the
accusations that have been made in the past. When I have more time I
will Google him and see what there is to see.
Lyle Fairfield - 05 Jan 2006 15:17 GMT
Lasy night in CDMA Larry and I held an election to choose a new judge.
You were not selected. So SHUT UP!
Steve - 05 Jan 2006 16:10 GMT
By your logic, anyone who is not a judge cannot speak/post. Therefore,
unless you were elected the new judge, you must abide by the same
restriction.
Lyle Fairfield - 04 Jan 2006 20:10 GMT
Compact Oxford English Dictionary

betray

 · verb 1 act treacherously towards (a person, country, etc.) by
revealing information to or otherwise aiding an enemy. 2 be disloyal
to. 3 unintentionally reveal; be evidence of.

I had to read and re-read your post to understand what you were
implying as David's sentence was perfectly clear to me. I use [betray]
=  [be evidence of] quite often.  It is something I grew up with, like
[to spleen against], or [boo-ee (buoy)];  is it merely local usage? As
David uses it and Oxford lists it, I think not.
David W. Fenton - 04 Jan 2006 19:50 GMT
> First of all, I've made it no secret that I do not understand or
> work with Access MDEs.
>
> Second, nearly every 'out of memory' or 'insufficient memory'
> error I have ever gotten was actually a result of the system
> running out of resources. . . .

That's what I said. That's what you *didn't* say. You said to add
RAM. RAM has nothing to do with resources *except* when extremely
limited (like 64MBs).

> . . . Perhaps your version of Windows was programmed by more
> malicious Microsoft coders than mine who one day decided to switch
[quoted text clipped - 9 lines]
> an 'out of memory' error...because it's using up all the memory
> available.

An infinite loop is not going to be resolved by adding memory unless
you add an infinite amount of RAM.

> Your response indicates a lack of proofreading.

You are an idiot.

<PLONK>

Signature

David W. Fenton                  http://www.dfenton.com/
usenet at dfenton dot com    http://www.dfenton.com/DFA/

 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.