Closed boluak closed 3 months ago
does using the Full DB Backup not help? i think items like this a DB script might be the best
Didn't help. It seems the error gets exported and re imported to the new dbase. Tried on many different platforms and hosts.
Is there any plan or possibility for a dbase cleanup/check routine? I noticed that deleting users does not re-assign unique keys hence user ID numbering is not contiguous.
Furthermore. When setting up new CCRM dbase for other parishes or importing data from other applications. E.g MSAcces or excel. CVS import seems the easiest option available.
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.
This issue was closed because it has been stalled for 15 days with no activity.
In one of my churchcrm production instance, i have more than 38 groups, with over 1000 members, i'm planning to export/import this to another instance due to database glitch. I cant proceed further as this will be a very tedious process of re-assigning this members to the different groups etc This will also help when I begin to implement additional church parishes/divisions into the present CRM database
If you have the ChurchCRM software running, please file an issue using the Report an issue in the help menu.
On what page in the application did you find this issue?
On what type of server is this running? Dedicated / Shared hosting? Linux / Windows?
What browser (and version) are you running?
What version of PHP is the server running?
What version of SQL Server are you running?
What version of ChurchCRM are you running?