[RESOLVED] Global Options in VBDOS

[AndyGable]

Hi all,

I hope someone can help. I have a basic vbdos app that I am working on and when my software boots it will load into a plan text mode and on screen it will show the status of the app (eg loading ini files etc)

I have a global bi file that has all my "global" variables (example I have one called PoSNumber and another called TransNumber etc)

I am not sure how I can access these from with in forms

I have tried to follow http://www.antonis.de/faq/qbmonfaq-d...233583164.html

But I can still not understand it.


If anyone has any simpler examples or sample code that would be most grateful.

Also does anyone know how I can make larger number on my form? (I was thinking about using this for the total due that is shown on screen).

[yereverluvinuncleber]

If I remember correctly you just include your .BI file in your main .BAS module and then all the defined globals will be available throughout the program.

[AndyGable]

If I remember correctly you just include your .BI file in your main .BAS module and then all the defined globals will be available throughout the program.

Hi @yereverluvinuncleber,
I tried that and when i went access for the example the PoSNumber I get either a blank field or a 0 in it

I'm happy to upload my VBDOS project here as it s a very basic on at the moment.

I did try this in QuickBASIC and I did not get very far with that at all

My Plan if i can get this to work is to introduct a VERY BASIC scanning system to my local shop (as at the moment they are using Pen and paper lol)

Kind regards
Andy

[yereverluvinuncleber]

Um, don't.

Just get a copy of TwinBasic and design your project using a dialect you are familiar with (BASIC) but then choose a supported environment (TwinBasic) where you can receive help and assistance.

Very few will be able to help you with VBDOS. It is a lost art.

If you can code in VBDOS then you can code in TwinBasic.

[AndyGable]

Um, don't.

Just get a copy of TwinBasic and design your project using a dialect you are familiar with (BASIC) but then choose a supported environment (TwinBasic) where you can receive help and assistance.

Very few will be able to help you with VBDOS. It is a lost art.

If you can code in VBDOS then you can code in TwinBasic.

Sorry for late replay I have been having some computer issues.

I would use TwinBASIC but i do not know how to do the screens correctly that was why I used VBDOS

I have moved all my globals to a new file called Global.BAS now Do I access them like global.terminalID or
do I need to stioll use the Dim shared TerminalID as string

beacuse when it boots up I get "Terminal ID set to : 100" and that is correct but when i go to the sign on screen
and i have Dim shared TerminalID as string and then on form open labTermID.caption = TerminalID this is blank
when the screen load

is this Dim shared creating a new version or do I need to use Dim const so it does not clear the data?

I know VBDOS is a OLD language but this is mainly for a hobby as I use to use this daily when I was a Teenager

Kind Regards to anyone who can help

Andy

[yereverluvinuncleber]

The dialect of BASIC is virtually the same, syntax &c, you will be familiar with it all. Some differences withe global variables but you will be able to transfer your skills to TB within a day or so.
The building of forms is virtually the same.

There is no help to be obtained from 95% of the people here who simply will not have experienced VBDos.

I have - but I can not remember the specific issues that arise from the use VBDos, so I am no use to you. I no longer have VBDoS so I can't even try things out to test for you.

You have my recommendation - go to TwinBasic and migrate your skills. If you have problems then we will help. You'll be flying within 2-3 days.

If you just want to recreate a retro app with retro tools, then I appreciate your efforts but you will need to find another retro-coding group to assist.

[AndyGable]

The dialect of BASIC is virtually the same, syntax &c, you will be familiar with it all. Some differences withe global variables but you will be able to transfer your skills to TB within a day or so.
The building of forms is virtually the same.

There is no help to be obtained from 95% of the people here who simply will not have experienced VBDos.

I have - but I can not remember the specific issues that arise from the use VBDos, so I am no use to you. I no longer have VBDoS so I can't even try things out to test for you.

You have my recommendation - go to TwinBasic and migrate your skills. If you have problems then we will help. You'll be flying within 2-3 days.

If you just want to recreate a retro app with retro tools, then I appreciate your efforts but you will need to find another retro-coding group to assist.

Does TB work still in dos or is this now a windows only version?

[yereverluvinuncleber]

Does TB work still in dos or is this now a windows only version?

Still? TB never worked in DOS.

[AndyGable]

Still? TB never worked in DOS.

Ohh sorry I must have miss understood I was looking for a DOS only solution that was why I want with VBDOS

[yereverluvinuncleber]

You never stated that. Try to be explicit and clear in your requirements so in future we can attempt to assist you. It is a waste of both our time and yours when you fail to let us know critical information.

I don't think we can help you further. My suggestion is that you find a retro computing scene where VBDOS users still exist.

[Peter Swinkels]

@AndyGable: Are you doing some retro-programming or is there a specific reason for a DOS-only solution?

As to your op:
1. If you declare your variables to be global at module level you should be able to refer to them from inside a form. Try using the GLOBAL keyword, or COMMON [SHARED]. If that doesn't do it, try DIM SHARED.
2. If you are referring to font sizes, you'll need to create your own custom method for text output.

[AndyGable]

@AndyGable: Are you doing some retro-programming or is there a specific reason for a DOS-only solution?

As to your op:
1. If you declare your variables to be global at module level you should be able to refer to them from inside a form. Try using the GLOBAL keyword, or COMMON [SHARED]. If that doesn't do it, try DIM SHARED.
2. If you are referring to font sizes, you'll need to create your own custom method for text output.

I'm just trying to fill. Gap in the retail system market between the top end systems and a cash register.

What I have done so far

In my global.bas file
Common shared PoSNumber as string

and when my system boots I have


Include once 'global.bi'
Then on the load screen in the form code I have

Dim shared PoSNumber as string

I then save the number 123 to PoSNumber


But when I show it on screen it's it blank

[Peter Swinkels]

Are there actually any cash registers running on DOS in need of new software?

To be honest it seems like you have no idea what you are doing and I doubt anyone with any sense would want some piece of crap software cobbled together by some noob in an ancient programming language running on something business critical as a cash register! LOL

[AndyGable]

My business was originally dos based when I opened it (2005) and we had a very stable and good dos application that I wrote.

The business is now using Linux (plus due to lack of use and using a new language I've started to forget my QuickBasic skills) and we have a very advanced system but I still feel that there is a need for a system that is not as advanced as our standard retail system.

The reason why I was thinking about dos was I could use FreeDOS as it would run on some very old hardware but so can a light Debian run on the same old hardware.

So rather than being abused by some people on this forum I'll just make a slim down version of our retail system in Linux.

[Peter Swinkels]

2005? DOS was eol by then. Linux is not a programming language. And you should forget those qb skills asap unless you want to do some retro stuff for the heck of it.

And if you want to conflate criticism in response to incoherent posts about some long dead language with abuse I am done here.