Hello Bruce, Yes, Randy's suggestion worked well. I had backed up my database but always good to remind! There was some work on Reports and Forms but I think it is all working now.
Unfortunately, it is a number supplied by other departments (using various systems) that we need to use to stay in sync with them. I should have done a full blown rewrite on this system years ago, but as I rose up in my department, there was less and less time to do so and I just kept adding on band-aids! Oh well. 20-20 hindsight! Lin On Thursday, April 17, 2025 at 8:14:21 PM UTC-7 Bruce Chitiea wrote: > Lin: > > Randy's approach is perhaps the simplest approach. > > Take a look at the attached .RMD file, which produces a export/printable > BROWSE list of all tableviewNames containing the columnName you provide. I > use this on my own databases. Print, or export the list to Excel, then use > as a checklist to follow your progress. > > It goes without saying ... so I'll say it ... be sure to perform a backup > of the database to a location where you can stress-less-ly retrieve it > before hacking and chopping. > > Because you're not changing tableNames, you should be able to open your > Forms and Reports so you can fix all the EEPs and Controls you broke. > [Ctrl-F] on the [Code] tab is your bestie. > > Questions. > > 1. You say these are "Unique" columns. Are your using UNIQUE keys as > (effectively) Primary and Foreign Keys to link your tables? > > 2. Does this UNIQUE value contain any meaning (e.g. "galaxyNo") beyond > being a simple, don't-mean-nuthin'-but-a-serial-number identifier for a row? > > 3. If it's just a serial number, mightn' it be best replaced with a BIGINT > (+- 999,999,999,999,999,999 (commas not included) ); or BIGNUM, as Robert > Diaz suggests? > > Might seem like a lot of work at the outset; but, this might re-connect > you with a lot of the victories you've earned over the years; and reveal > Easter-egg opportunities afforded by the new R:BASE versions. > > Best, Bruce > > Bruce A. Chitiea > SafeSectors, Inc. > 1142 S Diamond Bar Blvd # 442 > Diamond Bar CA 91765-2203 > > [email protected] > (909) 238-9012 m > > ------ Original Message ------ > From "randyp ctags.com" <[email protected]> > To "[email protected]" <[email protected]> > Date 4/17/2025 4:52:14 PM > Subject Re: [RBASE-L] - Data type question > > Rename *Column* in every table except one. Use a name like *Column1*. > Change the data type of the one remaining column. Rename each of the > others from *Column1* back to *Column*. It will change them to the new > data type. You may need to do this in the Database Explorer where columns > are defined. > > Will this lose the key structure and form and report connections? > > > ------------------------------ > *From:* [email protected] <[email protected]> on behalf of > Lin MacDonald <[email protected]> > *Sent:* Thursday, April 17, 2025 6:07 PM > *To:* [email protected] <[email protected]> > *Subject:* Re: [RBASE-L] - Data type question > > Sadly, it won't let me convert to any other type because it is tied to so > many tables. > > And, it was initially started on R:Base System V, LOL! Currently running > v. 10.5 > > On Thu, Apr 17, 2025, at 11:20 AM, Lin MacDonald wrote: > > I have a very old system. I began writing it in 1988 and have been adding > to it ever since. It has been so long that I don't remember how I set most > of it up! > > One of my Unique keys tying several tables together is a Real data type. > It will not let me enter more than 7 numbers (i.e. 9999999 or 9999.999) I > really need to be able to make it something like 9999999.9. So, add a > decimal point and 1 number. Is there any way to do that or am I stuck with > this length? > > thanks, > > Lin > > > -- > 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 visit > https://groups.google.com/d/msgid/rbase-l/0eb5c4ea-b662-49b9-b028-61a720930893%40app.fastmail.com > > <https://groups.google.com/d/msgid/rbase-l/0eb5c4ea-b662-49b9-b028-61a720930893%40app.fastmail.com?utm_medium=email&utm_source=footer> > . > > -- > 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 visit > https://groups.google.com/d/msgid/rbase-l/3778bc6d-024b-48ca-86cb-56f2cdb5a2e5%40app.fastmail.com > > <https://groups.google.com/d/msgid/rbase-l/3778bc6d-024b-48ca-86cb-56f2cdb5a2e5%40app.fastmail.com?utm_medium=email&utm_source=footer> > . > > -- > 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 visit > https://groups.google.com/d/msgid/rbase-l/PH0PR11MB5112E99CC8C75236F98E145CC7BC2%40PH0PR11MB5112.namprd11.prod.outlook.com > > <https://groups.google.com/d/msgid/rbase-l/PH0PR11MB5112E99CC8C75236F98E145CC7BC2%40PH0PR11MB5112.namprd11.prod.outlook.com?utm_medium=email&utm_source=footer> > . > -- 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 visit https://groups.google.com/d/msgid/rbase-l/f6ab7733-c983-4e30-8c62-07bc189240cen%40googlegroups.com.
