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

Converting dbf date to sql

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

    Converting dbf date to sql

    i am having trouble converting a date for SQL. bear with me, i'm no programmer and sql is way outside my comfort zone.

    firstly the UX is bound to a .dbf. in the table is a field where the user enters a value for 'number of months' this determines how long a fixed rate will last for a mortgage (thought this might help).

    i then convert this to an approx date with this (doesn't need to be exact) , which has been working fine.

    Code:
    if convert_type(ds.prod_ratemonths, "N") > 0 then
    		dim vdate as d
    		dim vmonths as n
    		dim vrdate as d
    
    		vdate=date()
    		vmonths=ds.prod_ratemonths
    		vrdate=addmonths(vdate,vmonths -2)
    i now want to write the value of VRDate to a SQL table which is not bound to the UX. i have done this with other dates ok but having trouble with this one, i am thinking because it has already been calculated as above, not sure.

    this works ok on another date value which get the data from the bound UX

    Code:
    dim ds as p = e.datasubmitted
    dim prodexch as C = ds.prod_dateonrisk
    
    args.set("prodexch", convert_type(prodexch,"D"))
    this doesnt work

    Code:
    dim reviewdate as C = VRDate - [COLOR="#FF0000"]produces no error executes .dbf code ok but doesnt write the record to the sql table[/COLOR]
    dim reviewdate as D = VRDate - [COLOR="#FF0000"]produces an error can't convert type c to d - doesnt execute any of the code[/COLOR]
    args.set("reviewdate", convert_type(reviewdate,"D"))
    i do then need to sort out a couple more fields related to this field which so far are as follows, they may work as is, not sure so thought i'd include it here.

    Code:
             dim review3 as D = VRDate-30
             dim review4 as D = VRDate-60
    	 dim review6 as D = VRDate-120
    	 dim prodenddate as D = VRdate + 60

    im almost there, just need to get this final bit sorted out. thanks for looking.

    #2
    Re: Converting dbf date to sql

    I think you convert_type in the args.set is getting in the way. I don't think it's needed. The following code works. I'm not pulling a number from a dbf table... but that's just a number and shouldn't make any difference. You're starting with a date type in vdate. Addmonths returns a date type. So... no need to convert it.

    Code:
    'if convert_type(ds.prod_ratemonths, "N") > 0 then
    dim vdate as d
    dim vmonths as n
    dim vrdate as d
    
    vdate=date()
    vmonths=24
    vrdate=addmonths(vdate,vmonths -2)	
    
    
    dim cn as sql::Connection
    dim args as sql::Arguments
    dim rs as sql::ResultSet
    dim flag as l
    
    args.set("myDate",vrdate)
    
    sql = "UPDATE tblCustomers SET ReportDate = :myDate WHERE Customer_ID = 1"
    
    flag = cn.open("::name::Test")
    
    flag = cn.Execute(sql,args) 
    
    cn.close()

    Comment

    Working...
    X