I am running into a problem with the "Backup table to Excel" buttons in the back-end of the database. It used to work perfectly fine, and now suddenly Excel won't open the file. It doesn't give me an error, at least not one that I can catch - I open the file, something flashes across the screen and then suddenly there's nothing open.
This is only a problem with some of the tables, which leads me to believe it's either a problem with the data or a problem with the way I set it up. But here are the things I've tried.
1. I added table fields via the phpMyAdmin interface, fields I DON'T want to be updated by the form so I did not reconnect the table to the form. I thought that might be a problem with the export, so I did the same thing on my dev site - new form, new field, no refresh. When I tried the Excel export there, it handled it fine! So that's not it.
2. Thought it might be the data, so I tried exporting it to CSV - both via phpMyAdmin and the ChronoForm button - but Excel is able to properly parse and import those files just fine - so it's not the data.
Obviously the workaround is to use the CSV but I'd like for the clients to be able to use the Excel button.
Ideally, I'd also like to be able to create a "Backup to Excel" button on the front end, I suppose using ChronoConnectivity, but I'm having massive issues trying to get the tutorial to work. I can't even save the posted form code because it prompts me to download the CSV file, and will never save the form code! It's probably an issue with my components being more up-to-date than the tutorial, so I am completely stuck. I need the back-end Excel button to work.
A related question - if I disconnect and reconnect the form to the table, does it completely wipe out the existing records? Similarly, if I create a table first and connect it later, will it properly read the table values as form-submitted values?
Thanks..
Jenny
This is only a problem with some of the tables, which leads me to believe it's either a problem with the data or a problem with the way I set it up. But here are the things I've tried.
1. I added table fields via the phpMyAdmin interface, fields I DON'T want to be updated by the form so I did not reconnect the table to the form. I thought that might be a problem with the export, so I did the same thing on my dev site - new form, new field, no refresh. When I tried the Excel export there, it handled it fine! So that's not it.
2. Thought it might be the data, so I tried exporting it to CSV - both via phpMyAdmin and the ChronoForm button - but Excel is able to properly parse and import those files just fine - so it's not the data.
Obviously the workaround is to use the CSV but I'd like for the clients to be able to use the Excel button.
Ideally, I'd also like to be able to create a "Backup to Excel" button on the front end, I suppose using ChronoConnectivity, but I'm having massive issues trying to get the tutorial to work. I can't even save the posted form code because it prompts me to download the CSV file, and will never save the form code! It's probably an issue with my components being more up-to-date than the tutorial, so I am completely stuck. I need the back-end Excel button to work.
A related question - if I disconnect and reconnect the form to the table, does it completely wipe out the existing records? Similarly, if I create a table first and connect it later, will it properly read the table values as form-submitted values?
Thanks..
Jenny
Hi Jenny,
Please email or PM me one of the 'faulty' Excel files so I can take a look.
Bob
Please email or PM me one of the 'faulty' Excel files so I can take a look.
Bob
what was the resolution to this? i think i'm having the same exact problem. a form that was backing up perfectly last week, is all of the sudden backing up an xls file that briefly flashes something, and doesn't open. but when i back up another form in chronoforms (same site), it works perfectly. this is particularly strange because i haven't touched anything in a week. thanks!
-wesley
-wesley
Hi kidnthehall,
There was no resolution to this particular case.
Various things can happen. If there are any errors in the output process these will be output to the Excel file and can mess it up. Someimtes by saving and opening it you can see what they are. There can be memory problems with large outputs - I saw one this week that ran fine with 2000 records but broke at 3000 - we fixed that by outputting to file in chunks of 1000 records.
There was also a very useful post recently by Erik (I think) who offered some small hacks to improve Excel export.
Bob
There was no resolution to this particular case.
Various things can happen. If there are any errors in the output process these will be output to the Excel file and can mess it up. Someimtes by saving and opening it you can see what they are. There can be memory problems with large outputs - I saw one this week that ran fine with 2000 records but broke at 3000 - we fixed that by outputting to file in chunks of 1000 records.
There was also a very useful post recently by Erik (I think) who offered some small hacks to improve Excel export.
Bob
oh well. i know it can't be a memory issue, there were only 18 records on the file. i just think it's weird that the other table we have from the site backs up xls just fine. we're able to open the csv in excel, and just save it as xls from there though. thanks!
This topic is locked and no more replies can be posted.
