Log In

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips Forums!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!
  • Students Click Here

*Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.

Students Click Here

Qbasic conversion

Qbasic conversion

Qbasic conversion

I have to convert an old  Qbasic app to Access. Could any of you all recommend a good OCx or library shareware tool that can help me convert the PEEK and POKE commands ?

RE: Qbasic conversion

I don't believe that such a tool exists. If it does exist, it certainly couldn't work very well. Microsoft allows us to read certain areas of memory (PEEK) with the CopyMemory API. We can, sometimes, use that API to write in the memory space owned by the application (POKE). But any attempt to change the contents of memory locations, for instance, in the first 640k of RAM, usually results in access violations and a dead program.

Suffice it to say that adding disk drives and a disk operating system to a personal microcomputer is guaranteed to increase its power dramatically.
CP/M and the Personal Computer

RE: Qbasic conversion

If it's a text program and you are poking to the screen,
you might consider PowerBasic console compiler.

RE: Qbasic conversion

If you are converting the (DOS) QBASIC program to Microsoft Access Application BASIC, there is no direct equivalent (Windows) behavior for those (DOS) PEEK and POKE actions.

What you must do is understand what the PEEKs and POKEs were actually doing (reading/writing characters on screen, messing with the DOS or BIOS data areas for some reason or other, like time delays or such, or something else) and program the functionally equivalent activity with new Application BASIC code in your Access program.

There is no peeking or poking memory in a windows program. It is not allowed by the operating system, and the same effects DOS users got by doing so cannot be done by directly accessing memory in Windows anyhow.

- Chuck Somerville

Red Flag This Post

Please let us know here why this post is inappropriate. Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework.

Red Flag Submitted

Thank you for helping keep Tek-Tips Forums free from inappropriate posts.
The Tek-Tips staff will check this out and take appropriate action.

Reply To This Thread

Posting in the Tek-Tips forums is a member-only feature.

Click Here to join Tek-Tips and talk with other members! Already a Member? Login

Close Box

Join Tek-Tips® Today!

Join your peers on the Internet's largest technical computer professional community.
It's easy to join and it's free.

Here's Why Members Love Tek-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close