Hi baudwalker,
I think I have a similar problem described here (
viewtopic.php?f=2&t=4098 ) - but have not gotten any solution so far.
There is some possibility I am considering at this time which I will describe in a second.
Some ideas first:
a) Why not follow the idea pbötcher's link (to the blog) holds, but extend the 'tags' table by another column 'customer'. Depending on how busy your table is, you might pull only those 'tags' from that table that match the customer and write those to the file.
b) You should take a look at the AG functions that are looking for that csv on your server. Probably it should be quite easy to change that function to use the name-extension you are suggesting. One drawback: That function will probably be overwritten when you regenerate your app in AG.
A quick check on one of my applications shows that this seems to be in the (not hooks directory) /tablename_dml.php file. Look for the function
There you find something like
Code: Select all
if(is_file(dirname(__FILE__).'/hooks/YourTablename.YourFieldName.csv')) {
$YourFieldName_data = addslashes(implode('', @file(dirname(__FILE__).'/hooks/YourTablename.YourFieldName.csv')));
You should be able to apply your suggestion there, something like this:
Code: Select all
if(is_file(dirname(__FILE__).'/hooks/YourTablename.YourFieldName.csv')) {
$mi = getMemberInfo();
$username = $mi['username'];
$YourFieldName_data = addslashes(implode('', @file(dirname(__FILE__).'/hooks/YourTablename.YourFieldName.' . $username . '.csv')));
Remember: The file will be overwritten when the app is being recreated.
.... well, so only theory, not tested!
Olaf