Thanks Javier.
I append the version # in DB explorer that you've shown when I unload a form or report to transfer from development db to production: dbname_Form_FormNameV60.frm That prevents name collision and also serves as backups for the form (or report) if I really blow things up.
Doug

On 5/22/2019 2:16 PM, [email protected] wrote:

Doug,

R:azzak provided the solution to obtain the version by code but you can always find it using the DB Explorer:

I use the version number to check which is the latest version but I wish there would be an extra field where we could enter our own version number and select which is the working version.

When I am working on and testing a form/report as I go along, every time I run the form/report from the designer after a change the form is saved (as it should be) and the version number is increased (again as it should be) by one and by the time I am done it might be on version 50 or 60 even when I am on only the second version of the upgraded form.

It would be handy to have a versioning system where various iterations of the form could be saved with the same name but a different user version number and one could be selected to run as default when the form/report name is called and one could go back to previous version if the new one has issues.…makes sense? Just thinking aloud…

Probably will be in the next update. J

Javier,

Javier Valencia, PE

O: 913-829-0888

C: 913-915-3137

-----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf Of Doug Hamilton
Sent: Wednesday, May 22, 2019 1:31 PM
To: R:Base List
Subject: [RBASE-L] - Form version number

I'm really beginning to rely on form and report version numbers.

Is there a property to get the version number of a form or report? (I

couldn't find one in RDocs).

Version # doesn't show in a form Ctrl-Alt-I.

It would be helpful in a development situation where I'm working on a

form and I need to check to make sure the production db has the most

recent form.

TIA,

Doug

---

This email has been checked for viruses by Avast antivirus software.

https://www.avast.com/antivirus

--

For group guidelines, visit http://www.rbase.com/support/usersgroup_guidelines.php

---

You received this message because you are subscribed to the Google Groups "RBASE-L" group.

To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].

To view this discussion on the web visit https://groups.google.com/d/msgid/rbase-l/29deb638-3d50-6b7a-1299-d8c34a3c1ba3%40wi.rr.com.

For more options, visit https://groups.google.com/d/optout.

--
For group guidelines, visit http://www.rbase.com/support/usersgroup_guidelines.php
---
You received this message because you are subscribed to the Google Groups "RBASE-L" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected] <mailto:[email protected]>. To view this discussion on the web visit https://groups.google.com/d/msgid/rbase-l/!%26!AAAAAAAAAAAYAAAAAAAAAO1ueGVb5zRMiwo7hebUe7jCgAAAEAAAAPs2XxxwjidEtVRebqBEGKwBAAAAAA%3D%3D%40vtgonline.com <https://groups.google.com/d/msgid/rbase-l/!%26!AAAAAAAAAAAYAAAAAAAAAO1ueGVb5zRMiwo7hebUe7jCgAAAEAAAAPs2XxxwjidEtVRebqBEGKwBAAAAAA%3D%3D%40vtgonline.com?utm_medium=email&utm_source=footer>.
For more options, visit https://groups.google.com/d/optout.

--
For group guidelines, visit 
http://www.rbase.com/support/usersgroup_guidelines.php
--- You received this message because you are subscribed to the Google Groups "RBASE-L" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/rbase-l/90ba1592-d8c5-abb6-b1bf-d917f802d253%40wi.rr.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to