asp in ms access or mssql question thanks

[melnet]

hi

1. there are have around 10k records in ms access. is the performance bad?

2.in ole object in ms acces, should i choose to save a pic into ole object or to save a path into text?

thanks for help...

 

[CassidyHunt]

I think your wanting to know if a 10K access file is going to slow performance and if it is better to use an OLE object or the path to display pictures.

I don't think 10K is a problem for Access. Really comes down to the number of records. I usually start having problems at 65,000 records.

As far as pictures go I always just handle it with a path because it is just way easier. You can use the img src tag and the path to pull up the picture instead of worring about another object.

If you need examples let me know.

Cassidy

 

[melnet]

1. a company have around 600 records in ms access, there have 10 records for update every week.so u think i choose db still is ms access?

2.a file is abc.jpg. i upload the abc.jpg to abc folder through ftp client s/w. however i only save a path to text field in ms access?such as abc/abc.jpg, right?

thanks for help.

 

[CassidyHunt]

Here is how I handle it:

<%
dim cn
dim rs

Set cn = Server.Createobject("ADODB.Connection")
Set rs = Server.CreateObject("ADODB.Recordset")

With cn
     .Provider = "Microsoft.Jet.OLEDB.4.0"
     .Connectionstring = "Path to Microsoft Access MDB"
     .open
end with

rs.open "Select * from TABLE",cn,3,3

%>
<Table>
<%
do until rs.eof = true
%>
<tr>
   <td><%=rs("Field")%></td>
   <td><img src="<%=rs("PictureField")%>></td>
</tr>
<%
rs.movenext
loop
%>

How I would store the data is using a virtual path. For instance if you ASP pages are stored in the folder webapp then I would have an image folder and have the record look like this:

image\picture.jpg

I think you will be just fine with Microsoft Access.

Let me know if you need more information.

Cassidy

 

[DreXor]

well in your questions, you said 600 records, 10 updated per week, that's not a problem , cause updating the records doesn't change the number of records. so you're ok there, UNLESS the 10 update is actually 10 additions, then you have 10 per week, to your 600, that's 40 per month, or roughly 600 per year ( with some spare room ),you're at roughly 1000 and adding roughly 1000 per year, you got at least a good 10 years on the DB as Access as long as the numbers dont change dramatically.

and as for the pic, it's probably better to store the path in the DB, one of which, keeps the db size down which helps performance, secondly, streaming from db isn't overly efficient, and thirdly, god forbid, there be a db problem, you dont lose all your images as well.
so yes, i'd store the path, or use a general path for the db, and say you have categories, make sub folders for each of these cats, then put the files in there, then only store the filename in the db, so if you ever need to rebuild the db contents, it'd be fairly easy at least on the image side to build from the contents of the folder based on the rules to create the folders, to create the db in reverse.

DreX
aKa - Robert