Alpha Software Mobile Development Tools:   Alpha Anywhere    |   Alpha TransForm subscribe to our YouTube Channel  Follow Us on LinkedIn  Follow Us on Twitter  Follow Us on Facebook

Announcement

Collapse

The Alpha Software Forum Participation Guidelines

The Alpha Software Forum is a free forum created for Alpha Software Developer Community to ask for help, exchange ideas, and share solutions. Alpha Software strives to create an environment where all members of the community can feel safe to participate. In order to ensure the Alpha Software Forum is a place where all feel welcome, forum participants are expected to behave as follows:
  • Be professional in your conduct
  • Be kind to others
  • Be constructive when giving feedback
  • Be open to new ideas and suggestions
  • Stay on topic


Be sure all comments and threads you post are respectful. Posts that contain any of the following content will be considered a violation of your agreement as a member of the Alpha Software Forum Community and will be moderated:
  • Spam.
  • Vulgar language.
  • Quotes from private conversations without permission, including pricing and other sales related discussions.
  • Personal attacks, insults, or subtle put-downs.
  • Harassment, bullying, threatening, mocking, shaming, or deriding anyone.
  • Sexist, racist, homophobic, transphobic, ableist, or otherwise discriminatory jokes and language.
  • Sexually explicit or violent material, links, or language.
  • Pirated, hacked, or copyright-infringing material.
  • Encouraging of others to engage in the above behaviors.


If a thread or post is found to contain any of the content outlined above, a moderator may choose to take one of the following actions:
  • Remove the Post or Thread - the content is removed from the forum.
  • Place the User in Moderation - all posts and new threads must be approved by a moderator before they are posted.
  • Temporarily Ban the User - user is banned from forum for a period of time.
  • Permanently Ban the User - user is permanently banned from the forum.


Moderators may also rename posts and threads if they are too generic or do not property reflect the content.

Moderators may move threads if they have been posted in the incorrect forum.

Threads/Posts questioning specific moderator decisions or actions (such as "why was a user banned?") are not allowed and will be removed.

The owners of Alpha Software Corporation (Forum Owner) reserve the right to remove, edit, move, or close any thread for any reason; or ban any forum member without notice, reason, or explanation.

Community members are encouraged to click the "Report Post" icon in the lower left of a given post if they feel the post is in violation of the rules. This will alert the Moderators to take a look.

Alpha Software Corporation may amend the guidelines from time to time and may also vary the procedures it sets out where appropriate in a particular case. Your agreement to comply with the guidelines will be deemed agreement to any changes to it.



Bonus TIPS for Successful Posting

Try a Search First
It is highly recommended that a Search be done on your topic before posting, as many questions have been answered in prior posts. As with any search engine, the shorter the search term, the more "hits" will be returned, but the more specific the search term is, the greater the relevance of those "hits". Searching for "table" might well return every message on the board while "tablesum" would greatly restrict the number of messages returned.

When you do post
First, make sure you are posting your question in the correct forum. For example, if you post an issue regarding Desktop applications on the Mobile & Browser Applications board , not only will your question not be seen by the appropriate audience, it may also be removed or relocated.

The more detail you provide about your problem or question, the more likely someone is to understand your request and be able to help. A sample database with a minimum of records (and its support files, zipped together) will make it much easier to diagnose issues with your application. Screen shots of error messages are especially helpful.

When explaining how to reproduce your problem, please be as detailed as possible. Describe every step, click-by-click and keypress-by-keypress. Otherwise when others try to duplicate your problem, they may do something slightly different and end up with different results.

A note about attachments
You may only attach one file to each message. Attachment file size is limited to 2MB. If you need to include several files, you may do so by zipping them into a single archive.

If you forgot to attach your files to your post, please do NOT create a new thread. Instead, reply to your original message and attach the file there.

When attaching screen shots, it is best to attach an image file (.BMP, .JPG, .GIF, .PNG, etc.) or a zip file of several images, as opposed to a Word document containing the screen shots. Because Word documents are prone to viruses, many message board users will not open your Word file, therefore limiting their ability to help you.

Similarly, if you are uploading a zipped archive, you should simply create a .ZIP file and not a self-extracting .EXE as many users will not run your EXE file.
See more
See less

Date Problem

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Date Problem

    In my Database I was updateing a Date field in the top (master) Table. The form used the Date Entry type which I like, but I would get a message about "field Requires time" or something, But it would NOT let me enter a date. After I entered the other dates I need to update I used the default browses selected the Record and entered the date.
    I am not sure about the message as I though A5 did not have a Time Field type. I entered about 500 changes (Dates) and only about 30 had this error. I could reenter the date in the form and it looked like it worked but if you selected the record again the date was blank.
    I hope I set something the caused this as I can NOT sell a system that sometimes it will not accept a Date.

    Thanks
    Philip Gerber

    #2
    RE: Date Problem

    Philip,

    Its hard to say what might be happening with out seeing it happen or at least a screen shot.

    If your telling us that you have entered 500 changes in the same table on the same field in the same form and 30 of them were rejected, I would have to say those 30 were typos or something to do with the data being entered.

    There is nothing wrong with A5 and dates. I have been using the product for over 14 years and never had a glitch with dates. This is basic stuff.

    If you can duplicate the problem, show us an example so we can see it happen too.

    Scott

    Comment


      #3
      RE: Date Problem

      Scott
      I hoped the problem was in my entry, I used the date format thing to enter dates, and my mouse is jumpy.
      One other thing that bothers me is the lack of a true "TIME" field. When you try to convert from access the import does not convert the field. I can not think of an acpplaction that does NOT use TIME. I hope A5 has an update for this type of entry. The other problem I may also have with the Date field is "on change" I save (re-write) the record, could this also cause a problem?

      Thanks
      Philip

      Comment


        #4
        RE: Date Problem

        Philip:

        Here is part of an old article I wrote for Alpha Five ver 4.

        In the process of creating database applications, one feature many of you will eventually need is the ability to record and/or calculate elapsed time. In order to calculate time differentials, you can use Alpha�s built in functions, totime() and toseconds().

        I think once you become familiar with these two functions, you will find it relatively easy to create the necessary calculations.

        CHARACTER: Totime(number_value, format_code, decimal_places)

        Use totime() to convert the number of seconds into hours and minutes for a character based display of time such as 9:45 am.

        NUMERIC: Toseconds(character_value) will return the number of seconds that have elapsed since midnight [86,400 seconds = 24 hours].

        This function will calculate the number of seconds elapsed whether you decide to use 24-hour formatting or the more conventional am/pm format. The result of the expression will be a numeric value.

        OK, now that we know these two functions exist, how do we use them to display and/or calculate elapsed time? Here is an example that calculates and displays the number of hours worked for your employees. You can get fairly sophisticated with these functions, but we will keep it basic and simple for the purposes of this article. I personally prefer using 24-hour formatting, but you can set up your own example using 12-hour [am/pm] formatting.

        --------------------------------

        I think the above should at least point you in the right direction.

        Philip, you can create a character based field and then manually enter time. Or you can also create a character field that is a "calculated field" using your computer's clock.

        Note:

        Some people like the idea of separting Date and time into their own fields, I happen to be one of them. I didn't care for Access's combo date/time fields. This is a matter of personal preference.

        Hope this helps get you started,
        Robert T

        Comment


          #5
          RE: Date Problem

          Robert
          Thank you, I work with when it happen not How long. What I do want to prevent is 13:01 AM. and system time field would prevent this or it should. I think setting a Button or something to set current time in a field would be very helpfull.
          Thanks
          Philip G.

          Comment


            #6
            RE: Date Problem

            Hello Philip:

            I'm sorry but I didn't understand your last message. Anyway, I think you should go to help and examine the documentation on
            the

            TIME() function

            I think that may be what you want.

            Robert T

            Comment

            Working...
            X