Search results

@GolfProRM Thanks for posting this. I've fiddled around with it a little, including putting in the missing Proc_Error, and my exported data is now nicely formatted to the end-users requirements. You've saved me a lot of time!

David That's a very thorough answer, for which thank you. Replication certainly does appear to be a tin of worms that is perhaps left alone in this case. I agree that the database doesn't sound well designed but I inherited the design and I can't go making wholesale changes as it's used too...

It strikes me that Replication is a path that should have gone down long before these databases were released into the wild. Can anyone confirm or contest this please? I'm still not convinced that it is the perfect solution, because each of the databases in the wild contain a different and...

I'll read up on Replication, with thanks. So far, it looks good, but would have been so much easier if they'd used it before creating the clones. The bit I need to read up on most now is the potential problems of changing the main database and the clones independantly. Thanks again

Long story short, I've inherited maintaining a database in which the Primary Key on most of the tables is Autonumber. Unfortunately, this database is used to collate data which is collected in clones of itself off-site, so I can't import data from the clones and maintain referential integrity...

Re: Need to check if textbox is empty.. Thank you both. I've no idea why my first two attempts didn't work but @RuralGuy's solution works a treat and that's all I'm really after.

@RuralGuy This worked for me too, such is the power of the forum search! However, could you try to explain to me why this solution works when the following didn't? IsNull(Me.TextBox) IsEmpty(Me.TextBox) Len(Me.TextBox) < 1 Me.TextBox = "" It's infuriating not to know, having tried so many...

I've been experiencing the same issue and read this answer with interest. Why does OnActivate work, while GotFocus, Load or Current don't? I've tried the last three, all to no acceptable level of consistency, and I'm off to try this suggestion now.

Gemma No. DataGood and DataFail are two saved queries that reference the temporary table DataTemp. They create the mutually exclusive datasets of matched and unmatched data, using the SQLSELECT * FROM DataTemp WHERE SerNo IS (NOT) NULLThere is nothing at all in the query that forces or implies...

FWIW, Version 12 is 2007. 11 is 2003 and 10 is 2002/XP, which is what I'd use as a default if you're wanting to make sure that whoever you're mailing it to can open it. You should use xlNormal instead of xlExcel12.

DJKarl Thank you for taking the time to write the code - it was easy to follow and worked a treat! I've no doubt I could have done it but it would have taken quite a while! I've adapted it slightly, by making it a function that I could call with parameters, saving coding time. I've attached...

The relevant line of code isDoCmd.TransferText acExportDelim, , "DataGood", Replace(strFilePath, "Import", "Export"), Truewhere strFilePath contains the full path and name of the imported file, DBImport.csv and just changes the output file name to DBExport.csv in the same relative location...

All numeric columns are being rounded, the data is good in the original import (checked in Excel and Notepad) and in the table before it's dropped. It's definitely the export process because exporting the table does exactly the same thing.

I'm beginning to get the feeling that I need to be looking at extracting a recordset and writing it field by field. Right or wrong?

A point that I perhaps didn't make crystal clear in my OP is that the import file can have any number of fields with whatever names you like, so long as the first one is called Member and they're all unique so as not to cause the import to fail. As a result, the export query is simplySELECT *...

Okay, I'll bite. The export is already based on a query rather than a table, to separate out the content of DBErrors.csv from DBExport.csv - making this slightly more detailed isn't a big deal but what's the best way of forcing the rounding, bearing in mind I'm already using a query?

I'm really trying to avoid that because the purpose of the module is to take anonymised scientific data and change the unique identifiers before running into another database elsewhere. If the other machine then has to convert these back to numbers, it's another step that's potentially another...

All I've searched these fora and know about export specifications but I can't figure out how to make them work in my instances. The story so far: I have a module which imports a file called DBImport.csv from the Desktop into a temporary table called DataTemp, after getting the user to confirm...

To qualify what @chergh has said, you'll probably also need to suppress warnings as, when saving a multi-sheet Excel file to CSV, you'll get a warning that CSV doesn't support multiple sheets. Also, the file the user will have open then will be the CSV, not the XLS, file. Be sure to save any...

Cancel this question - I solved it using the example on this page as a model. In short, I made the subform container invisible and removed the data source of the subform. Then added, in my code above, .RecordSource = "qrySearch" .Visible = true Now it works! I was also able to remove recalc...