Results 1 to 8 of 8
  1. #1
    2 Star Lounger
    Join Date
    Jan 2002
    Location
    Brugge, Belgium
    Posts
    144
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Eurosign in ms Access 2.0 (Ms Access 2.0)

    I have written a program in ms access 2.0, in wich i have a table named:" tblKlantMemo."
    This table has two fields :
    a<img src=/S/smile.gif border=0 alt=smile width=15 height=15> "KlntID" , the field on which the table is indexed and hold the clients number.
    b<img src=/S/smile.gif border=0 alt=smile width=15 height=15>" Info ", which is a memofield and serves is a holder for specific and normaly not displayed information of each of the clients.
    Often the information in this field are currency values with the eurosign "

  2. #2
    Super Moderator
    Join Date
    Aug 2001
    Location
    Evergreen, CO, USA
    Posts
    6,623
    Thanks
    3
    Thanked 60 Times in 60 Posts

    Re: Eurosign in ms Access 2.0 (Ms Access 2.0)

    I'm not sure it's Access 2.0 causing your difficulty, although official support for the eurosign (in currency fields) was added in Access 95 I believe. I think the problem with displaying the eurosign in a memo field may be related to the operating system. Is the PC running Access 2.0 running Windows 95 or latter, or is it running an earlier DOS based version of Windows?
    Wendell

  3. #3
    2 Star Lounger
    Join Date
    Jan 2002
    Location
    Brugge, Belgium
    Posts
    144
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Eurosign in ms Access 2.0 (Ms Access 2.0)

    Dear Wendell B.;

    First of all I would like to thank you very much for the quick reaction on my question.
    In your answer you wonder what version of windows i'm using.
    Well I'm using windows ME.
    As I mentioned before, the same program running on the same computer , but under MS Access 7.0, doesn't produce this problem, reason why I suspect MS Access 2.0 for this incompatibility.
    Greetings <img src=/S/help.gif border=0 alt=help width=23 height=15>

  4. #4
    Super Moderator
    Join Date
    Aug 2001
    Location
    Evergreen, CO, USA
    Posts
    6,623
    Thanks
    3
    Thanked 60 Times in 60 Posts

    Re: Eurosign in ms Access 2.0 (Ms Access 2.0)

    Well, that certainly suggests that Access 2 is the culprit. I didn't realize you were working on the same PC. Access 2 was designed to run on Windows 3.1/Windows for Workgroups, so it probably has it's own symbol table, rather than using the OS table. l dug through my Access 2 documentation and checked the symbol and there is no character assigned for ASCII 80x so it probably treats it as a non-printing character. All this makes sense as Access 2 was developed in 1993, and the euro was in the preliminary planning stages then. Does it cause major problems to upgrade the application - I would strongly suggest at least Access 97 as Access 95 (7.0) was fairly buggy, or Access 2000 which seems to be the most stable release yet.
    Wendell

  5. #5
    2 Star Lounger
    Join Date
    Jan 2002
    Location
    Brugge, Belgium
    Posts
    144
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Eurosign in ms Access 2.0 (Ms Access 2.0)

    Dear Wendell;

    You are more and more amazing me for the speed by which you react on a question and your willing to help another. Therefore my very very great appreciation.
    In my question I mentioned MS ACCESS 7.0. Unfortunately this was wrong, I meaned MS ACCESS 97.
    I'm using MS ACCESS 2.0, MS ACCESS 97 and MS ACCESS 2000.
    I just bought Window XP en MS OFFICE XP, so MS ACCESS2002 is also disposable.
    What about your advice, I only can tell you I'm on my way of upgrading the program to MS ACCESS 97.
    Reason why I still use MS ACCESS is very simple. The client for which I have written the program has only a license for MS ACCESS 2.0, and for the moment this client does not want to upgrade.
    I believe the only solution for the moment is to give my client the advice to add the word "EURO" behind the value in the memofield instead of the eurosign in front of the value.
    Your answer to my question will help me to persuade my client that:
    1) The problem I mentioned is not due incompetence of myself in programming but inherent to MS Access 2.0. I will show him your answer as a proof.
    2) It can help to persuade my client of the necessity to upgrade to MS Access 97 or later.
    Personally I prefer MS ACCESS 97, because I have some trouble to start again with something new as the ADO in MS ACCESS 2000 or MS ACCESS2002.
    I remenber a text written by Hellen Fedema in which she gives the advice not to move to ADO but to stay with DAO. Is this still the wright advice or Not ?

    Many many thanks

    Sincerely

    Pardo Jacques
    Belgium

  6. #6
    Plutonium Lounger
    Join Date
    Dec 2000
    Location
    Sacramento, California, USA
    Posts
    16,775
    Thanks
    0
    Thanked 1 Time in 1 Post

    Re: Eurosign in ms Access 2.0 (Ms Access 2.0)

    I question how long you'll have to choice not to learn ADO. You can still use DAO with Access 2000 and XP, but Microsoft has indicated that DAO will no longer be enhanced or updated. They also intend to discontinue support for Access 97 in the not too distant future, so I wouldn't recommend upgrading to that version.

    I'd suggest you start learning ADO now so you can work into it gradually. There's quite a learning curve, especially if you've been working in AccessBasic (Access 2.0) rather than VBA, but it makes sense once you get the hang of it.
    Charlotte

  7. #7
    Super Moderator
    Join Date
    Aug 2001
    Location
    Evergreen, CO, USA
    Posts
    6,623
    Thanks
    3
    Thanked 60 Times in 60 Posts

    Re: Eurosign in ms Access 2.0 (Ms Access 2.0)

    I'm with Charolette on DAP versus ADO. A couple of points too - if you are a small business, I don't believe you can legally upgrade to Access 97 these days - to the best of my knowledge MS will no longer sell client licenses and the retail product was all pulled two years ago. And you don't have to change to ADO in 2000/2002 as DAO is still there and at least in 2000 there are some things you can't do any other way than with DAO. The trick is to remove the reference to ADO and put in a reference to DAO.

    I believe the collective wisdom is that if you are upgrading an application that you stick with DAO unless there are compelling advantages to ADO, but if you are writing a new app, use ADO. Hope this helps.
    Wendell

  8. #8
    New Lounger
    Join Date
    Jan 2002
    Posts
    1
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Eurosign in ms Access 2.0 (Ms Access 2.0)

    Just a general comment, cannot help regarding the Euro problem. As I can see, I'm not the only one still using Access 2, the main reason being that applications remain small in size, very transportable; it's really been a terrific product. On the other hand, Access 2002 looks very good to me, I have just bought it, together with Access 2002 Inside-Out.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •