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

Printing problems Windows 2000 server

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

    Printing problems Windows 2000 server

    We have a network of 5 computers, with A5v4.5 installed on all of them. Three of the computers are running Windows 98, one is running Windows XP Pro, and the one where our application data is stored is running Windows 2000.

    We have 2 shared dot matrix printers attached to one of the Win98 computers to print our labels. When I print labels from the Win2000 computer or the WinXP computer, everything works fine. However, if I try to print from the Win98 computers it doesn't work.

    I have figured out a workaround, but it is a real hassle. All the computers except the Win2000 one, where the data is stored, are networked optimized. I can go into the "shadow" database stored on each computer, and change the label settings to the proper specifications, and then it will work. However, whenever I refresh the computer, the settings are messed up, and it will not work again until I adjust them. This is frustrating, because I need to frequently refresh, and we have multiple label layouts that need to be adjusted.

    I suspect this is something to do with differences between Windows 98 and Windows NT/2000/XP. Does anyone have any ideas?

    Thanks!
    Nathan

    #2
    RE: Printing problems Windows 2000 server

    Nathan,

    "I can go into the "shadow" database stored on each computer, and change the label settings to the proper specifications"

    Which specifications do you have to change?

    Bill
    Bill Hanigsberg

    Comment


      #3
      RE: Printing problems Windows 2000 server

      Hello Bill,

      Usually I have to change which printer to print to, and then since the labels are a custom page size, I also need to change the size of the labels in the label properties.

      It seems to me that the whole problem is based on selecting the proper printer. Everything worked fine when all our machines used Windows 95 or 98. This has only happened since we got a couple of computers which are NT based.

      Nathan

      Comment


        #4
        RE: Printing problems Windows 2000 server

        Nathan, instead of refreshing the shadow, try network optimizing, but be careful to network optimize *from* the server to the shadow, and not vice versa!

        -- tom

        Comment


          #5
          RE: Printing problems Windows 2000 server

          Nathan
          This is a very complicated problem. It is caused by the fact that Microsoft choose to change the addressing scheme for NT network printers than what it used for 95 & 98. This means that the address that 95 & 98 sees for a network printer is different than that of NT. The workstation that has the printers attached see the printer as a local printer. When you save the report on an NT machine and optimize 95 & 98 the address is no longer valid for the 95 & 98 machines so the report uses the closest printer that it has not the one you want to use. Changing it manually as you are doing is one way to solve the problem. If most reports and labels are printed to one of the network printers than you could make that printer the default printer on all of the workstations and set the reports or labels to print to the default printer this will mean that you won't have to modify those settings. You will only have to change the other ones. Alpha 5v5 will have a method to change the printer with xbasic.

          Comment


            #6
            RE: Printing problems Windows 2000 server

            I thought that I should make a clarification to my post. Win 95 & 98 identifies a network printer by it's shared name. NT, 2000 and XP by it's network address. I hope I didn't confuse anyone.

            Comment


              #7
              RE: Printing problems Windows 2000 server

              Allen,

              Thanks for your input. I was afraid that was the case. One more question. What did you mean by your comment, "Alpha 5v5 will have a method to change the printer with xbasic?" Does this mean that Alpha Five will be able to override the OS's interpretation of the printer addresses?

              Nathan

              Comment


                #8
                RE: Printing problems Windows 2000 server

                Nathan

                I just meant that you will be able to choose which installed printer to send a layout to using xbasic without user input just before printing the layout.

                Allen

                Comment

                Working...
                X