Recent content by Shep

After adding two columns to a SQL Server 7 (SP3) table we have found that a view from a linked server has stopped working with the message: SQL OLEDB supplied inconsistent metadata. An extra column was supplied during execution that was not found at compile time. This is not the first time we...

Cheers Tom, but I've already looked at SQL Mail. Like you say, it can respond to queries via email so I could get it to invoke a stored procedure but I don't see how it can help me retrieve, store + process an email attachment. Mark

Not looking for a spoon-fed, "here's the code to do it" answer, just a pointer in the right direction... I have a customer running a SQL Server 7 database with an Access 2000 front-end. He's very happy with it but I like to be pro-active and am looking at ways to improve it. One area...

Apologies in advance if I've come to the wrong place, but I'm trying to use the above DLL to create a dial-in connection but the blinking thing doesn't seem to want to register itself on NT (yet works fine on 95/98/2000). I have tried installing the Remote Access Service on my NT machine and...

nabs, The wildcard character in Access (all versions) is the asterisk (*) The wildcard character in SQL Server is percentage (%). I reckon your problem lies there rather than correlated queries. To prove it's nowt to do with correlated queries just try running the subselect in isolation. Shep

Phooey, In the example I mentioned above, all the controls were bound to an underlying record source. I've just done a test on a linked system on our network + you're right about the second LDB file being created (never noticed it before). BUT - I have also just tried the same thing using...

Phooey Like you say, when you open the front-end MDB you get a corresponding LDB. But you never open the other MDB file - the tables are all linked (File >Get External Data > Link Tables...). No errors, no problems & only one LDB file. Shep

Michael, Like I said in my post - I have done this several times with various payroll archives. The LDB file is created wherever the front-end MDB file is (eg C:\PayArch\) - it makes no odds where the linked tables are (eg D:\On_A_CD\). I even had one instance where I had 7 years worth of data...

Phooey, As Michael says, why not split your MDB in two and put the data on a CD and keep the front-end forms + queries etc on the user's hard-drive? You dont have to create a DBF file or anything like that - just have one MDB for the data and one for the software with all the tables linked...

jacquid, The way the help file read, I took it to mean that Access would only use an INI file if no specification name was included. Presumably you have included a specification for the export to use and it does exist in your database ? As an extra test could you try doing what the macro is...

Looking at the (Access 2000) help re TransferText Specification Name... The specification name for the set of options that determines how a text file is imported, exported, or linked. For a fixed-width text file, you must either specify an argument or use a schema.ini file, which must be stored...

To limit the records coming back from a select you can use TOP: Select TOP 10 * from tblTableName This will give you the first 10 records matching your criteria - not sure how you'd go about getting the next 10 though.. Shep

Just a thought, but could it be the actual data in the field that is causing the problem rather than the field itself ? For example, does it contain a carriage return / line feed combination (at position 126) that is stopping Excel displaying the data correctly when you come to view it ? Shep

RTFM 8-) or Format(Now(),"mmmm dd"", ""yyyy") Shep

Forms!frmMainForm!ctlSub.Form.RecordSource = SQL statement where... frmMainForm is the name of the main form ctlSub is the name of the subform control on the main form Shep