Community
Showing results for 
Search instead for 
Do you mean 
Reply

Timestamp and other usage issues.

New Member
Posts: 2
Country: United States

Timestamp and other usage issues.

Planning on using ACT! 2007, not installed yet.

 

Planning to import MS Access customer data (via .dbf export and then import) into ACT! and later export the data back to MS Access (via .xls export and then import), however when records are edited or added, does ACT! automatically timestamp the record, so on the changed/new record can be exported?

Platinum Elite Contributor
Posts: 14,384
Country: Australia

Re: Timestamp and other usage issues.

ACT! has Created and Edited fields that you can lookup. If you can modify the Access application is can directly read the ACT! tables via OLEDB - might be easier than exporting from ACT!. See: http://blog.glcomputing.com.au/2009/07/connecting-to-act-by-sage-data.html

 

Just a question will you want to import Access data for records already in ACT! and update them? If so, you can't do this via a normal import. You need to either use the ACT! SDK or an addon like itImport as I mention is the post above

 

If you need data to go both ways, having Access read ACT! via OLEDB and using itImport to bring the Access data directly to ACT! might be an option for you

New Member
Posts: 2
Country: United States

Re: Timestamp and other usage issues.

Basically this will be a one time use of ACT!.

 

The data will be imported from Access into a empty ACT! Database, modified while at a conference on a laptop, then later after the conference, the data will be exported back to Access for use in a web based application. The reason for this is that there is no guarantee of internet access at the conference.

 

Platinum Elite Contributor
Posts: 14,384
Country: Australia

Re: Timestamp and other usage issues.

Then bring them to ACT! via Export from Access to CSV and import to ACT!

 

Then have Access read them via OLEDB to query the records you want and bring the data back