By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
435,315 Members | 2,150 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 435,315 IT Pros & Developers. It's quick & easy.

Flat File import from Access 2007

P: 1
Im not a techie but run a small business in UK. We take instructions from clients from emails hard copy, spreadsheets etc and put them on excel templates then import to Access. A client wants us to accept work and report back in 'flat files'.

The files are not delimited by a common character but apart from the header and trailer they are of a fixed width (4096 character). The only issue we have with this is that a file can contain multiple record types (and therefore different formats of records) and I am not sure how to would get around this. Every file has its own particular extension.

Im trying to find out how to export from Access the required 'flat file' reports or how to convert excel spreadsheets exported from access perhaps with a bit of software I can buy to the right format. I must emphasise I am not a techie!
Any help greatly appreciated!
Sep 6 '07 #1
Share this Question
Share on Google+
2 Replies


NeoPa
Expert Mod 15k+
P: 31,494
You have (accidentally) posted this question in the Access Articles section. This is NOT an article.
I'm moving this to the main Access questions forum.

MODERATOR.
Sep 6 '07 #2

NeoPa
Expert Mod 15k+
P: 31,494
This doesn't sound trivial Dave I'm afraid :(
I would expect a fair amount of code to be developed for a requirement like this.
Unless you're quite experienced (I guess from what you say that you're not) you will need to get someone in to handle it for you (or possibly refuse the job). Another option is to explain to the client that, although they may not appreciate the difficulties, it does actually impose an enormous extra burden on the development side. There is very little support built into Access for such archaic ways of holding data. I say archaic, they were more common in the past, but were always associated with code to handle the 'specifics'.
Sep 6 '07 #3

Post your reply

Sign in to post your reply or Sign up for a free account.