Calculating Time Query

[Blaize]

Hi,

I'm having an issue trying to calculate time. Its okay if the value does not exceed 24 hours otherwise I get a date and hours listed. For example, I have a loop which looks through a table and adds up the time spent.

Dim TempCount As Date
    Dim DEVCount As Date
 
Do
 
        TempCount = rst!wtime
        DEVCount = DEVCount + TempCount
        rst.MoveNext
        i = i + "1"
 
    Loop Until rst!Anorder = 2
 

I have two other loops looping at AnOrder 2 and 3 and calculating their totals. They seems to be okay as their total are 9h:25m and 17h:35m. But DEVCount value for anOrder 1 is: 2/1/1900 22:24:00. I guess because its exceeding a 24hour period its adding days? Is there any way of getting a figure like 37h:44m or 57h:24m??

I know a way round it would be to set DEVCount as a date and time and calculate from there but it seems very long winded for what I think should be an easy task.

Please help!!

[Blaize]

Hi,

Nah its not the Now() function which is causing the issue I've replaced Now() with todays date. Compiled, saved works fine as a MDB file, build to an MDE file and get: "The expression On Click you entered..." error. Tried loads of things to get round it, even a query with all the 'If' statements etc and still get the same error. Either something really basic or critically wrong which is causing it to fail. What I can't get over is the fact that it works perfectly well as a MDB file.

Cheers,
James

[Blaize]

...but in answer to your question, adding in the line of code Call MsgBox(Now()) it displays the date & time, click on, then you get the error message,

Cheers,
James

[Scott Price]

This thread indicates that using a DAO recordset with a connected backend may require that you specifically open the backend first, before running the rest of your code.

The specific command given is

set db = dbengine(0).opendatabase("c:\foo\bar\mydata.mdb")

Obviously you'll need to change the c:\ path to reflect your database' location.

Regards,
Scott

[NeoPa]

...but in answer to your question, adding in the line of code Call MsgBox(Now()) it displays the date & time, click on, then you get the error message,

Cheers,
James

Ah, an answer to the question. Just what's required.

The MDE file is NOT the same as an MDB file. The rules are different. I'm not sure what they all are as I never use MDEs, but at least we now know where to look (your other tests provided little or no clues in that area).

I will need to revisit this later as I'm running late already and need to get home. Bump the thread tomorrow if I don't post something later tonight though. If I can't sort it then I'm sure we can find someone who can now we know where the issue lies.

PS. It looks as if Scott has already come up with something. let us know how you fare with this.

[Blaize]

I realise that MDE and MDB files are not the same but in terms of comiling a database you would think that if something is working as a MDB file that when you come to create an MDE file it should also work.

The query I created is held within the database whre I have the code. The backend has already connected. I did how ever add the command to test and I still get the same issue. I can't beleive such a straight forward command is causing so much of a headache?! I'm sure I've mentioned this before but I'm using Access 2000. The parameter I'm passign to the query is a Date value.

[NeoPa]

I realise that MDE and MDB files are not the same but in terms of comiling a database you would think that if something is working as a MDB file that when you come to create an MDE file it should also work.
...

I wasn't trying to differentiate between the files, but between how (and if) the compiled project works.
You are right in that one would like to hope that they would behave in a consistent manner in both forms. However, the unfortunate fact is that they don't. There are rules to follow when converting an MDB to an MDE. You should find these explained in your help system. Never having used an MDE myself, I'm not sure what the rules are, I'm simply aware they exist.

This is all a bit similar to what happens when you upgrade from one version to another. There should be compatibility. In most cases there is not.