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

image file reference field on runtime network

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

    image file reference field on runtime network

    Hi forum..

    I have my app installed on a network with 3 pc's
    all running windows xp pro with the latest patch.
    now, here is the problem.....

    I have my database with the runtime files installed on workstation1. Sharing the database folder. This work station is acting as a server but someone is working from it.

    I have the runtime files installed on the other 2 workstations which are mapped in to workstation1. All have be optimized, Now if i change the picture in the image filed in the database from workstation1 it doesn't change on the other 2 workstations. If i change the text fields that updates the other pc's with no problem but the image doesn't.

    Now if i got to the other work stations and change the image in the image field, it updates to both workstations, but not workstation1 the(acting server).

    Now i know that i shouldn't have my database with the runtime files on the acting server together, but my customer only has 3 pc's and want to share the database and use all 3 pc's as workstations.

    Am i doing something wrong here?

    Thank for any advice..

    #2
    Re: image file reference field on runtime network

    Hi there

    Does the image display correctly if you hit F5 (refresh display) on the offending machine?

    Regards

    Glen Schild
    Glen Schild



    My Blog

    Comment


      #3
      Re: image file reference field on runtime network

      No, it doesn't display at all. I can close the app and re open it and only the text fields are updated.

      any ideas?

      Comment


        #4
        Re: image file reference field on runtime network

        The image file reference field stores the full location of the image say:

        c:\databasefolder\images\imagename.jpg

        I presume when it fails on the other machines the text that appears in the fields instead of the image shows the mapped location for the images where Alpha Five is expecting to find the images. say

        s:\databasefolder\images\imagename.jpg

        So when you update an image on one of the "non server" workstations it changes the location to that seen by that machine and thereby confusing the server machine.

        I think that made sense? If this is the case then presumably the only way to resolve would be to ensure that all three machines map to the drive in the same way?

        Regards

        Glen
        Glen Schild



        My Blog

        Comment


          #5
          Re: image file reference field on runtime network

          Glen, I was thinking along the same lines - in situations where I have say 3 users or so on a LAN, and one of them is acting as the server, then I create a map the same way I do on the other machines. And I also shadow that computer the same way I do the others. Although, we always have a partition on the drive that we use for the app - like on the main computer it would likely be drive "D" since "C" is the first. And if the other workstations are mapped to "Drive D" as "S", then I also create a map on the main computer to "Drive D" as "S."
          Cole Custom Programming - Terrell, Texas
          972 524 8714
          [email protected]

          ____________________
          "A young man who is not liberal has no heart, but an old man who is not conservative has no mind." GB Shaw

          Comment


            #6
            Re: image file reference field on runtime network

            Here is a page in the help about 'Aliases'. It seems to be relevant to this discussion. I have not used it so can not comment further. Just thought I would bring it to your attention.
            Tim Kiebert
            Eagle Creek Citrus
            A complex system that does not work is invariably found to have evolved from a simpler system that worked just fine.

            Comment


              #7
              Re: image file reference field on runtime network

              Maybe this can help a little as I was not able to understand all of what I read above/

              1. Use a pathe to data like \\servername\datafoler\data.adb. Mapping drives can and usually does cause problems.

              2. if you are going to use 3 computers and one of them is a server. That is ok(not great), put your data in a shared folder. access it from the other 2 computers by shadow and also from the server by shadow, making your shadowed fold different from the data folder. Example: my shadowed folders on all workstations are drive:\ups55 and the server folder is server:\ups55s. The shadowed tables on the server are in drive:\ups55 just like the other work stations. It just cuts down on problems. seems to go faster too.
              Dave Mason
              [email protected]
              Skype is dave.mason46

              Comment


                #8
                Re: image file reference field on runtime network

                Maybe this can help a little as I was not able to understand all of what I read above/

                1. Use a path to data like \\servername\datafoler\data.adb. Mapping drives can and usually does cause problems.

                2. if you are going to use 3 computers and one of them is a server. That is ok(not great), put your data in a shared folder. access it from the other 2 computers by shadow and also from the server by shadow, making your shadowed fold different from the data folder. Example: my shadowed folders on all workstations are drive:\ups55 and the server folder is server:\ups55s. The shadowed tables on the server are in drive:\ups55 just like the other work stations. It just cuts down on problems. seems to go faster too.

                3. If the picture files need to reside on the server so all can see from the workstations, then the path should be to there, but for portability use the function(I believe a5.GET_MASTER_PATh()) for that path+the \picfolder\pic as needed. This way if the jpg, or ir change it will retriev the new one. Path looks like a5.GET_MASTER_PATh()+"\\apic\"P"+acct+".jpg"
                a. I do this in field rules. You cannot make it a calculated field but you can make it in the data entry - simple condition. Insert the proper path and it sould always work. Mine happens to use a "P"+ACCT+".jpg" as the pic is saved in the folder with a P+ the acct number and we only use jpg right now.

                Hope this helps

                .
                Last edited by DaveM; 05-18-2008, 10:31 PM.
                Dave Mason
                [email protected]
                Skype is dave.mason46

                Comment


                  #9
                  Re: image file reference field on runtime network

                  I was able to get this to work by making the image folder a seperate shared folder from the database folder. example: when you click on network places from the other work stations, you would see a shared folder for the database and a shared folder for the images, all coming from the acting server. As long as everyone chooses the image from this folder it would update the other stations. I didn't have to create a shadowed database from the acting server to get it to update. I guess the only problem i would have is, if the client decided to move the database to an actual stand alone server each record's image field would have to be updated to the newly shared image folder.

                  Thanks for all the help and suggestions.
                  Kool :)



                  Originally posted by glenschild View Post
                  The image file reference field stores the full location of the image say:

                  c:\databasefolder\images\imagename.jpg

                  I presume when it fails on the other machines the text that appears in the fields instead of the image shows the mapped location for the images where Alpha Five is expecting to find the images. say

                  s:\databasefolder\images\imagename.jpg

                  So when you update an image on one of the "non server" workstations it changes the location to that seen by that machine and thereby confusing the server machine.

                  I think that made sense? If this is the case then presumably the only way to resolve would be to ensure that all three machines map to the drive in the same way?

                  Regards

                  Glen

                  Comment


                    #10
                    Re: image file reference field on runtime network

                    Originally posted by TheseNutts View Post
                    I guess the only problem i would have is, if the client decided to move the database to an actual stand alone server each record's image field would have to be updated to the newly shared image folder.

                    Thanks for all the help and suggestions.
                    Kool :)
                    I think that is the purpose of the Alias feature I pointed out. The path would be stored as [some_alias]imagename.jpg . Then if the path changed you only need to change the definition of the alias.
                    Tim Kiebert
                    Eagle Creek Citrus
                    A complex system that does not work is invariably found to have evolved from a simpler system that worked just fine.

                    Comment

                    Working...
                    X