[AccessD] VBA Runtime Error

...I've never understood why something so fundamental isn't the default for 
every new module ...its not like MS is doing anyone any favors or closing 
any options :(

...but what the heck ...we got a transparent gui, ribbons, and sharepoint in 
A2K7 ...who needs real fixes, much less common sense.

...I was reading the blog of one of the Access team members and he started 
going on about how he knew what real developers needed because after all 
they had to write the sample mdbs themselves.

...sorta choked me up ...lost a diet coke all over the screen, I did.

...and then there was the team lead all indignant about repeated requests 
for autocorrect to be off by default ...wanted everyone to know just how 
much work he'd put into that feature and that it worked right fine in his 
opinion :(

William

----- Original Message ----- 
From: "JWColby" <jwcolby at colbyconsulting.com>
To: "'Access Developers discussion and problem solving'" 
<accessd at databaseadvisors.com>
Sent: Wednesday, August 16, 2006 3:59 PM
Subject: Re: [AccessD] VBA Runtime Error


> Boy howdy, I second THAT one.  Option explicit is a requirement in my 
> book.
>
>
> John W. Colby
> Colby Consulting
> www.ColbyConsulting.com
>
> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com
> [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of MartyConnelly
> Sent: Wednesday, August 16, 2006 2:54 PM
> To: Access Developers discussion and problem solving
> Subject: Re: [AccessD] VBA Runtime Error
>
> You might want to put statement Option Explicit in all your modules to 
> force
> variable declaration and recompile
>
> Kaup, Chester wrote:
>
>>This is a single database thus front end back end. It stops in the same
>>place every time. I think I may have solved the problem. I did not dim
>>a date variable - just let access do it. I dimmed it and code is now
>>running.
>>
>>
>>-----Original Message-----
>>From: accessd-bounces at databaseadvisors.com
>>[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of JWColby
>>Sent: Wednesday, August 16, 2006 10:40 AM
>>To: 'Access Developers discussion and problem solving'
>>Subject: Re: [AccessD] VBA Runtime Error
>>
>>Is it consistent?  Perhaps a corrupt FE or BE.  Is it intermittent or
>>one time?  Perhaps a bad NIC or other network problem.
>>
>>
>>John W. Colby
>>Colby Consulting
>>www.ColbyConsulting.com
>>
>>-----Original Message-----
>>From: accessd-bounces at databaseadvisors.com
>>[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Kaup,
>>Chester
>>Sent: Wednesday, August 16, 2006 11:18 AM
>>To: Access Developers discussion and problem solving
>>Subject: [AccessD] VBA Runtime Error
>>
>>Had the following error come up when running VBA code in a module. Line
>>it stopped on set a variable to a table field in a native table. What
>>does it mean?
>>
>>
>>
>>Run-time error '-2147417848(80010108)'
>>
>>
>>
>>Automation error
>>
>>The object invoked has disconnected from its clients.
>>
>>
>>
>>Chester Kaup
>>
>>Engineering Technician
>>
>>Kinder Morgan CO2 Company, LLP
>>
>>Office (432) 688-3797
>>
>>FAX (432) 688-3799
>>
>>
>>
>>
>>
>>No trees were killed in the sending of this message. However a large
>>number of electrons were terribly inconvenienced.
>>
>>
>>
>>--
>>AccessD mailing list
>>AccessD at databaseadvisors.com
>>http://databaseadvisors.com/mailman/listinfo/accessd
>>Website: http://www.databaseadvisors.com
>>
>>
>>
>
> --
> Marty Connelly
> Victoria, B.C.
> Canada
>
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>
> -- 
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>