Space for version?

[Heathbo]

A runtime I created will be going through beta testing in a few days. When creating a runtime, is there a place to put what version it is. For example, saying this is version Beta 1.01.

[Heathbo]

A runtime I created will be going through beta testing in a few days. When creating a runtime, is there a place to put what version it is. For example, saying this is version Beta 1.01.

[Heathbo]

A runtime I created will be going through beta testing in a few days. When creating a runtime, is there a place to put what version it is. For example, saying this is version Beta 1.01.

[QuinTech]

Hi, Heath. Your best bet will probably be to add a field to your main file to record the version number. Are you looking to get this onto a splash screen? If so, then you'll have to make your own one of those as well, with a "Go To Layout (Splash Screen)-Pause for 3 seconds-Go To Layour (Main Page)" script.

Jerry

[QuinTech]

Hi, Heath. Your best bet will probably be to add a field to your main file to record the version number. Are you looking to get this onto a splash screen? If so, then you'll have to make your own one of those as well, with a "Go To Layout (Splash Screen)-Pause for 3 seconds-Go To Layour (Main Page)" script.

Jerry

[QuinTech]

Hi, Heath. Your best bet will probably be to add a field to your main file to record the version number. Are you looking to get this onto a splash screen? If so, then you'll have to make your own one of those as well, with a "Go To Layout (Splash Screen)-Pause for 3 seconds-Go To Layour (Main Page)" script.

Jerry

[Lee Smith]

Hi Jerry,

I had this made up, but had to leave for a few minutes, so there is some cross over.

Hi Heathbo

Here are some of my thoughts:

Put the number on a welcome page, and/or any Instruction Document. Handy for keeping track of the revisions and dates.

You need a field for showing the Beta name and number, I would lock it so that the user can not change it, and I would place it on the default page. You will need to reflect the data in this field in reports that the testers will be sending you concerning any bugs, or feature requests. I would set up a separate file for this, and make it available from all layouts and files in the Beta Copies. Use a scripts, maybe even attach it to a button, and have the Scripts reflect the layout name and file, as part of it.

I would also make the name of the Folder the same as the file (i.e. Beta v1.1, Beta v1.2, Beta v2.1, etc.). You and the testers don't want to wipe out previous versions every time you issue a new one. I have had to refer back to these older versions for many reasons. Mainly, not all testers will be on the current set of files when reporting bugs and features, and you will want to confirm that this was a bug and not corrected in the previous version. I keep them when testing for others, to ensure that the developer has understood or made the changes I have suggested. Sometimes in the rush to respond and get a finished product out, you (developer) can get lost on the bug and features.

HTH

Lee

[Lee Smith]

Hi Jerry,

I had this made up, but had to leave for a few minutes, so there is some cross over.

Hi Heathbo

Here are some of my thoughts:

Put the number on a welcome page, and/or any Instruction Document. Handy for keeping track of the revisions and dates.

You need a field for showing the Beta name and number, I would lock it so that the user can not change it, and I would place it on the default page. You will need to reflect the data in this field in reports that the testers will be sending you concerning any bugs, or feature requests. I would set up a separate file for this, and make it available from all layouts and files in the Beta Copies. Use a scripts, maybe even attach it to a button, and have the Scripts reflect the layout name and file, as part of it.

I would also make the name of the Folder the same as the file (i.e. Beta v1.1, Beta v1.2, Beta v2.1, etc.). You and the testers don't want to wipe out previous versions every time you issue a new one. I have had to refer back to these older versions for many reasons. Mainly, not all testers will be on the current set of files when reporting bugs and features, and you will want to confirm that this was a bug and not corrected in the previous version. I keep them when testing for others, to ensure that the developer has understood or made the changes I have suggested. Sometimes in the rush to respond and get a finished product out, you (developer) can get lost on the bug and features.

HTH

Lee

[Lee Smith]

Hi Jerry,

I had this made up, but had to leave for a few minutes, so there is some cross over.

Hi Heathbo

Here are some of my thoughts:

Put the number on a welcome page, and/or any Instruction Document. Handy for keeping track of the revisions and dates.

You need a field for showing the Beta name and number, I would lock it so that the user can not change it, and I would place it on the default page. You will need to reflect the data in this field in reports that the testers will be sending you concerning any bugs, or feature requests. I would set up a separate file for this, and make it available from all layouts and files in the Beta Copies. Use a scripts, maybe even attach it to a button, and have the Scripts reflect the layout name and file, as part of it.

I would also make the name of the Folder the same as the file (i.e. Beta v1.1, Beta v1.2, Beta v2.1, etc.). You and the testers don't want to wipe out previous versions every time you issue a new one. I have had to refer back to these older versions for many reasons. Mainly, not all testers will be on the current set of files when reporting bugs and features, and you will want to confirm that this was a bug and not corrected in the previous version. I keep them when testing for others, to ensure that the developer has understood or made the changes I have suggested. Sometimes in the rush to respond and get a finished product out, you (developer) can get lost on the bug and features.

HTH

Lee

[pjdodd]

I would create a specific About page that contains the version number etc...