Bruce, if it helps, single user does allow you to have two sessions of R:Base open at once – either same or different databases – but from the same “seat” only.
That facility is absolutely essential to me – especially at upgrade time but also when troubleshooting. Regards, Alastair. PS: backups should be your first religion <g>! Been “saved” many a time... From: Bruce Chitiea Sent: Friday, August 17, 2012 8:03 PM To: RBASE-L Mailing List Subject: [RBASE-L] - RE: RCharts cannot find variable value Alastair: That totally goes into my tool kit, as backup is my new religion. Thanks much. For now, the issue is my RBase xTreme / RCharts environment in which single-user licenses prevent simultaneous connection to the target database. Solved by RBucks when available. The issue at hand here is RCharts 'choking' on the first variable of the first sub-select statement of the first view used as feedstock to the final view in the RCharts-connected database from which the chart draws its values. 'Solved' THAT by retooling the view-creation routine to project that final view to a table suggestively named: 't_chart_ ...' which then feeds the chart. The table gets dropped at the beginning of the view-creation routine when next run. Totally avoids the real problem - the choke - buts gets me down the road. Bruce -------- Original Message -------- Subject: [RBASE-L] - RE: RCharts cannot find variable value From: "Alastair Burr" <[email protected]> Date: Fri, August 17, 2012 10:47 am To: [email protected] (RBASE-L Mailing List) Bruce, this may be totally irrelevant to your needs – if so, ignore it! Two things you could do IF you want to avoid creating a permanent table in place of a temp one: First, you could create the temp table as you want, then unload it to a file; do your disconnect/connect, then create & load a temp table from the file into the original database. A bit more radical if you are going to use the data in the temp table then discard or need to keep for future reference it is to create a new database along with the similar unload process as above (thus cutting out the load), connect to the new database and view your data. When you’re done disconnect and connect to your original and carry on. You can then erase the new database whenever you want or keep for reference. I copy one of my databases, it’s very small, when I do backups so that I can connect to the copy and unload from the original and my other databases, update backup info in the copy then unload that data and load it into the original when all the backups are done. It might sound complicated but it’s not and it works well for me. Just some ideas, good luck Regards, Alastair. From: Bruce Chitiea Sent: Friday, August 17, 2012 6:05 PM To: RBASE-L Mailing List Subject: [RBASE-L] - RE: RCharts cannot find variable value All: Don't know if the formatting came through legible or not, but never mind. Figured out to PROJECT the source view to a permanent table to survive the disconnect and source the chart without variable interaction. Thanks Bruce
