[AccessD] quick help needed

That happens to me all the time.
Besides describing the problem in good enough detail we have put it in
understandable English which gives additional time to think of a solution.

Helmut


-----Ursprungliche Nachricht-----
Von: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com]Im Auftrag von Lembit
Soobik
Gesendet: Donnerstag, 17. Juni 2010 21:12
An: Access Developers discussion and problem solving
Betreff: Re: [AccessD] quick help needed


LOL,
John, that's the magic of AccessD ;)
In fact, I guess almost everyone on the list has experienced the fact that,
once you describe your problem in good enough detail, you see the problem
point and can solve it.

Lembit

----- Original Message -----
From: "John Clark" <John.Clark at niagaracounty.com>
To: "Access Developers discussion and problem solving"
<accessd at databaseadvisors.com>
Sent: Thursday, June 17, 2010 8:19 PM
Subject: Re: [AccessD] quick help needed


> Sorry...I guess more info would be in order...I'm just sweatin' a little
> over this.
>
> The record source for this report is a query ("qryCertInfo"). This query
> is based on two other queries...the first being a table of "county
> information" ("qryCntyInfo") and the 2nd ("qryCert2Print") which is based
> off the current record that is up on the entry form. This form based query
> chooses its single record from "[Forms]![frmDataEntry]![ssn]" on the form,
> and, "[forms]![frmDataEntry]![sfrmCerts].[Form]![Certificate Date]" on
> that form's sub-form.
>
> As I am typing this, I'm wondering if I may not have found my own
> solution...might it be because there is yet to be any data on the subform?
> There is nothing in,
> "[forms]![frmDataEntry]![sfrmCerts].[Form]![Certificate Date]", so maybe
> it is fudgin' up things.
>
> BUT...why does it work sometimes? If this is the case, it shouldn't work
> at all.
>
> ...NEVERMIND...I found it! It IS what I just described. For some reason,
> she was forgetting to enter a certification date, and the program was
> choking on that. So, I showed her what the problem was...and now I have to
> add something to check for this.
>
> Thanks for the help...sometimes I just need to talk it out w/someone. It
> tends to scare those around me, w/I talk amongst myself ;o)
>
>>>> Gary Kjos <garykjos at gmail.com> 6/17/2010 11:11 AM >>>
> Well what is the record source for the report?  Is it using a filter
> of some kind when you call the report from the form to select that
> same record for the report?  That would seem to be where to focus.
> Perhaps a dubug mode session to see what is in fields used for the
> filter?
>
> GK
>
> On Thu, Jun 17, 2010 at 9:56 AM, John Clark
> <John.Clark at niagaracounty.com> wrote:
>> I just rolled out a new program yesterday and it worked quite well. I
>> tested it and ran it through the course, and everything seemed to go as
>> planned. I am fully aware that no matter how much you test something, as
>> soon as you turn it over to the user(s), they WILL find the bugs, and I
>> warned them that this will happen and we'll work through anything that
>> comes up...it is easy w/this group, because they literally sit right
>> beneath my office...we share a server, a switch, everything is the same,
>> so I can basically mimic everything they do.
>>
>> Well, it was installed yesterday. After installing it, I watched as the
>> user entered her first bit of information. It was pretty uneventful, but
>> we did get a bug...my fault actually, as I borrowed some new code that I
>> liked for my nav buttons and I wasn't really comfortable w/it...that was
>> bad enough, but this actually made some previously entered code buggy as
>> well. All in all though, nothing huge and I just had some little bugs to
>> fix. And, they had some customers come in throughout the day, and all
>> went well.
>>
>> BUT...after I left for the day, they got another customer and the program
>> would not cooperate. Basically, this program takes in student information
>> and prints a certificate that they take to their schools. This
>> certificate, which printed previously, no longer found information off
>> the form. It prints, but it is blank where any information from the form
>> goes...it prints from the current form. Now it says, "Run-time error
>> '3021' No Current record."  And, that is not all the time...what they
>> hey?! There IS a current record...it is the one on the screen that I am
>> pushing the button for!
>>
>> Any clues here would be greatly appreciated...I'm a bit under the gun
>> here.
>>
>> Thanks!
>>
>> John Clark
>>
>>
> --
> 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